You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.
Over the last year of iterations for edge cases, the capture analysis has gotten pretty complicated, and code even more so.
It would be useful to create a formal specification for the analysis and validate all the cases with the current implementation. It might not be the worst idea to refactor the code to mimic the formal analysis more closely.
The text was updated successfully, but these errors were encountered:
2229: Rewrite/Refactor Closure Capture Analaysis
While handling all the differnet edge cases the code for the captur analysis got pretty compicated. Looking at the overall picture of the edge cases the rules can still be layed out simply.
Alogithm: https://hackmd.io/D3I_gwvuT-SPnJ22tgJumw
r? `@nikomatsakis`
Closesrust-lang/project-rfc-2229#52
Implementation part of rust-lang/project-rfc-2229#53
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Over the last year of iterations for edge cases, the capture analysis has gotten pretty complicated, and code even more so.
It would be useful to create a formal specification for the analysis and validate all the cases with the current implementation. It might not be the worst idea to refactor the code to mimic the formal analysis more closely.
The text was updated successfully, but these errors were encountered: