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

Thought: Change persistence model for Closures #5

Open
briandamaged opened this issue Dec 20, 2010 · 0 comments
Open

Thought: Change persistence model for Closures #5

briandamaged opened this issue Dec 20, 2010 · 0 comments

Comments

@briandamaged
Copy link
Owner

Currently, closures are compiled and persisted temporarily each time they are used. This is handy for code that is performed infrequently (ex: top-level drivers, etc), but it results in a lot of wasted cycles for functions that are called repeatedly. Consider changing the caching mechanism so that the generated code is persisted for a longer period of time. In other words: allow individual closure instances to reference the same code.

Here's the real question: Will the caching actually be more efficient than just recompiling each time?

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

No branches or pull requests

1 participant