Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SA1313: Parameter '__' must begin with lower-case letter.
See original GitHub issueThe following code snippet is OK in StyleCop 4.6, but not in StyleCopAnalyzers:
Action<object, object> b = (_, __) => { };
The warning output is warning SA1313: Parameter '__' must begin with lower-case letter.
StyleCopAnalyzers seems to be OK with a single underscore, but not two underscores. I assume this is due to https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/StyleCop.Analyzers/StyleCop.Analyzers/NamingRules/SA1313ParameterNamesMustBeginWithLowerCaseLetter.cs#L86 explicitly checking for a single underscore.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:22 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
To add my two cents to this.
WPF has a very common type
RoutedEventHandlerso seeing(_,__) => {...}when responding to events is rather normal.While it would be better if C# supported
_as a syntax for ignored parameters (like other languages). Using multiple underscore to communicate parameters as being unused is still better than using comments to communicate unuse. It also falls into line with alot of the teaching out there for functional programming.The stable 1.1.118 fixes this, and is making my code better in new ways.