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

Deterministic Destruction (GC) #26

Open
iwillspeak opened this issue Feb 3, 2019 · 0 comments
Open

Deterministic Destruction (GC) #26

iwillspeak opened this issue Feb 3, 2019 · 0 comments
Labels

Comments

@iwillspeak
Copy link
Owner

Currently values allocated, at the moment just Strings, are never deallocated.

A first-cut of ensuring deallocation could use reference counting on each allocated object. Emitted code will need to keep track of when an item enters and leaves scope, along with when the object is copied. A possible optimisation would be to use escape analysis to store values which never live longer than the current function on the stack rather than the heap.

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

No branches or pull requests

1 participant