Skip to content
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

Deep updates in F* blows up memory. #1098

Open
karthikbhargavan opened this issue Nov 5, 2024 · 0 comments
Open

Deep updates in F* blows up memory. #1098

karthikbhargavan opened this issue Nov 5, 2024 · 0 comments
Labels
engine Issue in the engine f* F* backend

Comments

@karthikbhargavan
Copy link
Contributor

We do not have a small reproducer, but deep updates in F* are causing a memory blow up.

Two of these patterns are:

  • a.coefficients[i] += 3
  • a[i][j] += 3

These are translated into nested updates (which is correct) but chaining two such updates already uses up gigabytes of memory when typechecking with F* and adding more updates cases OOM errors in F*.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine Issue in the engine f* F* backend
Projects
None yet
Development

No branches or pull requests

2 participants