-
Notifications
You must be signed in to change notification settings - Fork 76
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
Evaluation priority idea #93
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At his talk in San Diego yesterday, @guillaumebrunerie showed that making certain functions opaque can help with evaluating nasty terms. The problem is that sometimes the opaque functions have to be unfolded.
Here's my idea: annotate functions with evaluation priority levels. Using the convention that higher numbers correspond to higher priorities and that the default priority level is 0, we can replace opaque functions with priority level (-1) functions. Then the evaluator would treat them as opaque until it gets stuck, then try to evaluate them.
We can also play with partial evaluation by setting everything below a certain priority level as opaque.
The text was updated successfully, but these errors were encountered: