Skip to content

Draft: Use alloc_mode with uniqueness for block allocations in lambda #1

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

Closed

Conversation

anfelor
Copy link
Owner

@anfelor anfelor commented Oct 3, 2024

This PR tracks adding the alloc_mode back to lambda, this time with uniqueness information. I have opened it in this repository to make sure we get a clean diff (as the overwriting branch is behind main and we depend on oxcaml#3108).

I am still unsure about some parts of this. 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?

@mshinwell
Copy link

@anfelor why was this closed - is this change being done elsewhere now?

@anfelor
Copy link
Owner Author

anfelor commented Oct 31, 2024

@mshinwell Yes, this PR is now at oxcaml#3116; I have already adjusted the link in the wiki.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants