Clarity on style guide
See original GitHub issueWhat style guide should be followed?
It looks like the original codebase followed Brad Adam’s guide that is vastly different to the CoreFx’s one, that is indirectly recommended via the docs (developer guide -> coding guidelines -> C# coding style).
Do we use this.variable or _variable?
Do we place usings inside or outside namespaces?
Do we sort class members (I actually very much like that rule)?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Style guide comparison to achieve clarity in writing
To achieve the best results for clarity in writing, we are doing a style guide comparison to get the best results for technical...
Read more >Writing With Clarity and Style: A Guide to Rhetorical ...
The aim of this book is to help contemporary writers learn the names of these devices and understand how they lend themselves to...
Read more >Style and Clarity
Style and Clarity · 1. Write naturally, use only words you understand. · 2. Eliminate unnecessary words and phrases. · 3. Write actively,...
Read more >Writing with Clarity and Style: A Guide to Rhetorical ...
The book shows you how to use dozens of classical rhetorical devices to bring power, clarity, and effectiveness to your writing.
Read more >What Is A Style Guide And Why Is It Important?
1. Clarity in communication · 2. Increase the efficiency of your organization · 3. Focus on the customer · 4. Decrease operational costs...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Style cop is an institutionally acceptable option. My personal opinion is that I would rather these things me automagically fixed at edit-time ; there should be a way to keep uniform style and avoid additional work necessary on the part of developers.
Now it all makes sense, thank you all