-
Notifications
You must be signed in to change notification settings - Fork 509
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
SA1009 and C# 7 Tuples #2267
Comments
Yeah, we need to evaluate all new C# 7 syntax in the context of current rules. @vweijsters @pdelvo Any thoughts on how to start testing these scenarios? We could create a unit test project that references a version of Roslyn that understands C# 7, or we could use a different version of Roslyn for the main library and the unit tests. Or perhaps we create a new "v2.0" branch where we require such a version of Roslyn, and don't accommodate these features in the 1.x branch at all? |
See also #2268 |
I would be in favor of having a branch, as we will probably have to do some major changes to the analyzers, the code fixes, and the unit tests. I haven't checked yet, but I assume that the new language constructs will have new syntax classes as well, and these will not be present in older versions. I personally am not a big fan of having a lot of We may need to maintain two versions of the project in parallel for (quite) some time, I'm not convinced yet that we can merge the code bases for these, but that could change once we've done the work for v2.0. |
SA1009 is indicated at the closing brace of tuples inside generics. For example for the following function definition:
In my opinion, this use case should be allowed and no SA1009 generated.
The text was updated successfully, but these errors were encountered: