Use alloc_mode with uniqueness for block allocations in lambda #3116
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR tracks adding the
alloc_mode
back to lambda, this time with uniqueness information. I am still unsure about several bits in this PR and am sharing it so that we can discuss (perhaps in person) what is correct and what has to change. In particular:alloc_mode
onlparam.mode
andlfunction.ret_mode
inlambda.mli
?alloc_heap_aliased
andalloc_local_aliased
bindings below correct?