Naming convention of parameters of value tuples

[WhiteBlackGoose]

Am I correct, that the accepted naming convention for parameters of value tuples is camelCase? If not, skip this post :P

If so, then isn't that inconsistent with

1. public property convention (PascalCase)
2. Item1, Item2 etc. default properties' names?

I used to write them all camelCase, but now I'm more inclined to write Pascal, which makes it overall more consistent with other code, but at the same time inconsistent with other value tuples. So I'm a bit lost.

Why camelCase?

[CyrusNajmabadi]

Why camelCase?

They were designed to mimic passing around a parameter list, just wrapped into a single value.

Note, if you want a different making style, then fell free. It's your code, do what you feel is best.

[WhiteBlackGoose]

Thanks

[jnm2]

This was hashed out at great length in dotnet/runtime#27939 when the BCL added their first tuple-returning API and set the precedent to pascal case. And now, for example, StyleCop defaults to the BCL precedent.

[WhiteBlackGoose]

I'm a bit lost in that long discussion... am I right, that the overall agreement is to use PascalCase for public API, and camelCase for local use?

[jnm2]

I don't think local use was determined in that thread, but for consistency I've been using exclusively pascal case so that dotting looks the same everywhere.

[WhiteBlackGoose]

Awesome. Thanks a lot