-
Notifications
You must be signed in to change notification settings - Fork 4k
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
EnC - Allow capturing new variables in lambdas #54672
Milestone
Comments
dotnet-issue-labeler
bot
added
Area-Compilers
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Jul 7, 2021
jinujoseph
added
Concept-Continuous Improvement
and removed
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Jul 9, 2021
This was referenced Jan 24, 2022
Implemented by #70418 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment we don't allow capturing a variable in a lambda if it wasn't already captured in the baseline compilation. We should consider allowing this, especially in the case where there is already an existing capture of some kind, as the runtime change is a field insert, which is otherwise supported.
This issue is referenced from code.
eg: https://wengier.com/DecompilationDiffer/#5VBNC4JAFJxbEPQflk5KEd0rL0J0qJNBB-kgJhKYQmop4X9vdtPSsFNCh1j27fuaeW8nRYwjQvgQsJAzSuDhhBkG6MNFAIe5mFVTZW7KivJcEBF9oLeBprDnJ5uNPa3DjM_KmL6sJHxz6A2WJueLW2IFMt4Fb8i9rnyXSOm7mDfmGZyvkVf2GrRDrNgf8ET0BUZq7gRbxlYNJzF6-du2LUz2h5wUkckjfqeQUqO1YvDIkDVYKmShogI97vtJ43eFpb5dqFvX9pfKPqrVljam3FpX__5O57rK_6Jxm4pd63gH
The text was updated successfully, but these errors were encountered: