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

Shrink the GSS based on whether calls can still be performed #18

Open
eddyb opened this issue Aug 21, 2018 · 0 comments
Open

Shrink the GSS based on whether calls can still be performed #18

eddyb opened this issue Aug 21, 2018 · 0 comments

Comments

@eddyb
Copy link
Member

eddyb commented Aug 21, 2018

With the current (breadth-first) evaluation strategy, we can use the union of the input ranges of all the scheduler entries as a conservative approximation of the range of the input that is still being parsed and correctly assume that any further calls to be made, will be entirely within that range.
Therefore, any call nodes that are (partially) outside of the remaining input range can be removed.

This, just like #17, may interfere with #12, #13, #16 etc. (but the impact is less clear).

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