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

Two ways to tighten upper bound #139

Open
mlb2251 opened this issue Aug 24, 2022 · 1 comment
Open

Two ways to tighten upper bound #139

mlb2251 opened this issue Aug 24, 2022 · 1 comment

Comments

@mlb2251
Copy link
Owner

mlb2251 commented Aug 24, 2022

Two alternatives that I think might be pretty effective at tightening the bound:

  1. We can tighten the local upper bound at each location using any arguments that have already been decided. I think this information might already be freely available so it might be cheap. Even though final abstractions tend to take very small arguments, bigger abstractions might not
  2. If you dont do the above bound tightening, then the bound is equal to the subtree size meaning ancestor match locations subsume lower ones so you can discard the lower ones and not include them in the bound since they cant improve it any more than "delete the parent tree"
@mlb2251
Copy link
Owner Author

mlb2251 commented Nov 25, 2022

honestly curious if this will make it actually worse as a heuristic bc it correlates less w match locs?

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

No branches or pull requests

1 participant