-
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
Spec seems to allow readonly fields of instances other than 'this' to be assigned in constructors
#1235
opened Dec 12, 2024 by
jnm2
When is a unary operator not a unary operator?
type: bug
The Standard does not describe the language as intended or implemented
#1215
opened Nov 20, 2024 by
jskeet
How to explain extension method invocation when the
this
parameter involves type parameters?
#1203
opened Nov 12, 2024 by
jcouv
Foreach processing for types implementing IEnumerable<T> is problematic
#1188
opened Oct 16, 2024 by
svick
Check that name shadowing with "simple" local variables is still prohibited
#1131
opened Jun 12, 2024 by
jskeet
nameof can refer to a variable "early"
type: bug
The Standard does not describe the language as intended or implemented
#1111
opened May 16, 2024 by
jskeet
Documentation for exception thrown within The Standard does not describe the language as intended or implemented
when
expression
type: bug
Exclude quadruple slash
////
and /***
from documentation comments
#1079
opened Apr 14, 2024 by
KalleOlaviNiemitalo
Assignment rules for properties/events/fields should account for generic receivers
#1078
opened Apr 12, 2024 by
jcouv
Standard should state that patterns can be tested in any order
status: needs triaging
#1074
opened Apr 8, 2024 by
BillWagner
Better conversion from expression should prefer delegate types with non-void return type
#1072
opened Apr 5, 2024 by
jcouv
[C# language specification 7th edition] Incorrect rule for definite-assignment state for || expressions
#1070
opened Mar 31, 2024 by
fmdkara
Example in 18.4.6 is incorrect: calling an ambiguous-looking interface member can work...
type: bug
The Standard does not describe the language as intended or implemented
#1062
opened Mar 27, 2024 by
jskeet
“Defensive” copies – standardising a compiler strategy or language semantics?
#1053
opened Mar 4, 2024 by
Nigel-Ecma
Remove list of implications of dynamic/object identity conversion from 8.7
type: clarity
While not technically incorrect, the Standard is potentially confusing
#1034
opened Jan 11, 2024 by
jskeet
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-11-28.