-
Notifications
You must be signed in to change notification settings - Fork 87
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
Label
Projects
Milestones
Assignee
Sort
Issues list
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)
Hiding an inherited reserved method signature - No warnings if
new
keyword is not used
#1194
by logeshkumars0604
was closed Dec 7, 2024
Null forgiving operator grammar issues
type: bug
The Standard does not describe the language as intended or implemented
Nested class within a static class - static or non-static by implicit?
#1189
by logeshkumars0604
was closed Oct 28, 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
§15.4 states that constant members can be reference types.
#1165
by praeceptum
was closed Aug 29, 2024
Auto properties section explains property initializers by linking to array initializers
#1163
by jnm2
was closed Aug 23, 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
Annex C.2 isn't necessarily correct (in terms of only being things in ISO)
#1146
by jskeet
was closed Oct 9, 2024
14 Namespaces section doesn't describe file scoped namespace declarations
#1113
by knutwannheden
was closed May 16, 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
[Nullable Reference Types] Specify new generic constraints necessary for nullable reference types
#1091
by BillWagner
was closed Dec 11, 2024
[Nullable Reference Types] Specify syntax for nullable reference types
#1090
by BillWagner
was closed Oct 9, 2024
Previous Next
ProTip!
Updated in the last three days: updated:>2025-02-07.