We should Inform people about appropriate use of analyzers (#3934)
* We should Inform people about appropriate use of analyzers as per #3925 * Update README.md Co-authored-by: Fred Silberberg <fred@silberberg.xyz>
This commit is contained in:
parent
8bcdc05af8
commit
3f6a61b29b
|
@ -30,6 +30,8 @@ Discussions that are short and stay on topic are much more likely to be read. If
|
|||
- Stick to the topic of the discussion. If a comment is tangential, or goes into detail on a subtopic, start a new discussion and link back.
|
||||
- Is your comment useful for others to read, or can it be adequately expressed with an emoji reaction to an existing comment?
|
||||
|
||||
Language proposals which prevent specific syntax from occurring can be achieved with [a Roslyn analyzer](https://docs.microsoft.com/en-us/visualstudio/extensibility/getting-started-with-roslyn-analyzers). Proposals that only make existing syntax optionally illegal will be rejected by the language design committee to prevent increased language complexity.
|
||||
|
||||
## Proposals
|
||||
Once you have a fully fleshed out proposal describing a new language feature in syntactic and semantic detail, please [open an issue for it](https://github.com/dotnet/csharplang/issues/new/choose), and it will be labeled as a [Proposal](https://github.com/dotnet/csharplang/issues?q=is%3Aopen+is%3Aissue+label%3AProposal). The comment thread on the issue can be used to hash out or briefly discuss details of the proposal, as well as pros and cons of adopting it into C#. If an issue does not meet the bar of being a full proposal, we may move it to a discussion, so that it can be "baked" further. Specific open issues or more expansive discussion with a proposal will often warrant opening a side discussion rather than cluttering the comment section on the issue.
|
||||
|
||||
|
|
Loading…
Reference in a new issue