We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Although dotnet/csharplang#3548 expresses informally the intent to make some scope changes to the language in support of records, the records specification at https://github.com/dotnet/csharplang/blob/master/proposals/records.md still contains no modification to the name lookup rule in https://github.com/dotnet/csharplang/blob/master/spec/expressions.md#simple-names that would be needed to describe the intended language impact.
See also #44687. Once the spec is written the compiler would need to be implemented (if there is any mismatch) and tested against the specification.
/cc @AlekseyTs @agocke
The text was updated successfully, but these errors were encountered:
This issue is too general to be actionable.
Sorry, something went wrong.
@AlekseyTs The ask is to update the records speclet with the changes from this PR: #44906
From offline discussion, the speclet was already updated to include the information.
jcouv
No branches or pull requests
Although dotnet/csharplang#3548 expresses informally the intent to make some scope changes to the language in support of records, the records specification at https://github.com/dotnet/csharplang/blob/master/proposals/records.md still contains no modification to the name lookup rule in https://github.com/dotnet/csharplang/blob/master/spec/expressions.md#simple-names that would be needed to describe the intended language impact.
See also #44687. Once the spec is written the compiler would need to be implemented (if there is any mismatch) and tested against the specification.
/cc @AlekseyTs @agocke
The text was updated successfully, but these errors were encountered: