-
Notifications
You must be signed in to change notification settings - Fork 173
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
Memory management in nested lambdas is not working properly #1416
Comments
copying over some thoughts from chat: this is similar to issue #597 but what's probably happening here is For the double-free issue, the problem is sort of the opposite phenomenon where a variable that should be treated as the same is being treated as distinct. This might be because of the state popping happening in |
Allocating inside a lambda an using the value in a nested lambda results in double free:
With Matches
Using
match
confuses the compilerCompiler output:
While using match-ref results in a badly emitted C source:
Output:
The text was updated successfully, but these errors were encountered: