Comments (3)
The implementation of this rule is a little different from the original StyleCop version when it comes to the sections of a "for" loop. In the previous version, you would be nudged towards writing an "infinite" for loop as:
for (;;)
{
}
Other variants would trigger a violation of SA1002. By contrast, the only way to adhere to the rule now appears to be:
for (; ;)
{
}
which raised a violation of SA1002 in the previous version. Is this deliberate? The same difference is apparent if you add just an initializer to the loop.
I'm posting several queries of this style as I migrate an existing solution to use the StyleCop Analyzers; is it generally intended that the rules that existed in the previous version should preserve their behaviour?
from stylecopanalyzers.
@jackwhelpton It's normal for replies to "get lost" when they are added to issues that are already closed. You should open a new issue for items like this to make sure at a minimum that they get documented.
📝 Your comment is indirectly related to #633.
from stylecopanalyzers.
Raised #1489: cheers.
from stylecopanalyzers.
Related Issues (20)
- SA1611 not throwing warning for additional parameter in the "private" method if documentation not available for it HOT 4
- SA1009 ans SA1024 clashses in the middle of a line HOT 4
- SA1009 - Behavior in Switch expression
- SA1106 false positive on class with no body HOT 5
- Ability to have multiple (hierarchical) configuration files HOT 2
- SA1003 conflicts with SA1010 for new style collection initialisation. HOT 2
- SA1009 conflicts with SA1024 for primary constructors with parent classes. HOT 2
- SA1313 incorrectly suggests that record property names should start with a lower-case letter. HOT 3
- SA1206 suggests a non-idiomatic placement of the required modifier. HOT 6
- New Rule Proposal: SA1208 but for Microsoft.*
- Documentation for SA1604 contains an irrelevant line
- SA1514 is falsely reported when documenting types declared in the global namespace HOT 1
- When using the new collection initializer [] no SA1010 should be raised. HOT 4
- SA1402 is not raised when declaring multiple types in a file-scoped namespace HOT 1
- SA1402 doesn't recognize records HOT 5
- SA1516 is reported between extern alias and global using HOT 5
- Extend SA1129 to cover parameterless struct constructors HOT 1
- SA1015 false positive on object initializer HOT 3
- SA1012 incorrectly reported on opening brace in List Pattern matching HOT 2
- Add option to detect unused using HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stylecopanalyzers.