-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorconfig naming convention for tuple element names #38705
Comments
As far as I know there is no official decision on this. The [docs](https://docs.microsoft.com/en-us/dotnet/csharp/tuples use camelCase. see DotNetAnalyzers/StyleCopAnalyzers#3019 |
@kofifus The official decision is referenced in dotnet/corefx#35595 and confirmed at https://github.com/dotnet/corefx/issues/33553#issuecomment-531420515 which mentions that they are working on docs. |
thanks @jnm2 maybe it's just how I read it but nothing in those discussion seems very official .. |
It's as official as any decision that has been made between the C# language design team and the framework design team. You'll have to be patient about the docs. (For example, the docs still have pre-.NET 4.0 advice about how to implement IDisposable, when SafeHandle is the only thing you should be using for unmanaged resources.) |
Note that this naming style is unrelated to the design guideline. From the perspective of Roslyn's naming style feature, PascalCase and camelCase are equally valid options for this, with neither having priority. We definitely want to support the user specifying their preferred style for these elements. 👍 |
Now that we have settled on the guidance of pascal case for tuple element names (dotnet/corefx#35595, https://github.com/dotnet/corefx/issues/33553), it would be nice to have a
tuple_element
symbol kind to which a naming convention can be applied.https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-naming-conventions?view=vs-2019#kinds-of-symbols
The text was updated successfully, but these errors were encountered: