You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: