Skip to content

Use alloc_mode with uniqueness for block allocations in lambda #3116

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 1 commit into
base: overwriting
Choose a base branch
from
Draft

Use alloc_mode with uniqueness for block allocations in lambda #3116

wants to merge 1 commit into from

Conversation

@anfelor
Copy link
Contributor

@anfelor anfelor commented Oct 4, 2024

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:

  • Do we need an alloc_mode on lparam.mode and lfunction.ret_mode in lambda.mli?
  • Are all of the alloc_heap_aliased and alloc_local_aliased bindings below correct?

@anfelor anfelor requested a review from goldfirere October 4, 2024 19:18
@anfelor anfelor mentioned this pull request Oct 31, 2024
Closed
@anfelor anfelor marked this pull request as draft November 11, 2024 16:07
@anfelor anfelor added uniqueness lambda Lambda language changes labels Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@goldfirere goldfirere Awaiting requested review from goldfirere

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

lambda Lambda language changes uniqueness

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@anfelor