Skip to content

Issues: dotnet/csharpstandard

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Document
#1197 by GIgako19929 was closed Dec 11, 2024
Post/pre inc/dec "typically"? type: bug The Standard does not describe the language as intended or implemented type: formatting The Standard has incorrect formatting (or a typo)
#1196 by Nigel-Ecma was closed Nov 14, 2024 C# 8.0
Null forgiving operator grammar issues type: bug The Standard does not describe the language as intended or implemented
#1190 by jskeet was closed Dec 11, 2024 C# 8.0
Typ0
#1169 by Playgirlkaybraz11 was closed Sep 9, 2024
Minor tweaks to the handling of right-associative operators type: clarity While not technically incorrect, the Standard is potentially confusing
#1166 by RexJaeschke was closed Sep 5, 2024
Parameters #3: Duplicate normative parameter-kind definitions type: clarity While not technically incorrect, the Standard is potentially confusing
#1160 by RexJaeschke was closed Oct 2, 2024
Parameters #2: Alternate Terms for a Parameter Kind type: clarity While not technically incorrect, the Standard is potentially confusing
#1159 by RexJaeschke was closed Oct 2, 2024
Parameters #1: The use of “formal” in “formal parameter” type: clarity While not technically incorrect, the Standard is potentially confusing
#1158 by RexJaeschke was closed Oct 2, 2024
Add whitespace in C.3 type: clarity While not technically incorrect, the Standard is potentially confusing
#1151 by jskeet was closed Nov 3, 2024
Pre-processing line directive
#1118 by logeshkumars0604 was closed Dec 11, 2024
Unicode escape sequence in identifiers meeting: proposal There is an informal proposal in the issue, worth discussing in a meeting
#1107 by logeshkumars0604 was closed Jun 6, 2024
[Nullable Reference Types] Provide informative notes and examples on diagnostics meeting: discuss This issue should be discussed at the next TC49-TG2 meeting
#1094 by BillWagner was closed Nov 20, 2024
[Nullable Reference Types] Specify nullable flow analysis lattice meeting: discuss This issue should be discussed at the next TC49-TG2 meeting
#1093 by BillWagner was closed Oct 2, 2024
[Nullable Reference Types] Specify behavior for nullable analysis attributes meeting: discuss This issue should be discussed at the next TC49-TG2 meeting
#1092 by BillWagner was closed Nov 20, 2024
ProTip! Updated in the last three days: updated:>2025-02-07.