-
Notifications
You must be signed in to change notification settings - Fork 19
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
Test code #31
Test code #31
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Had a suggestion and a question
…acyclic egraphs. Disabled the faster-greedy-dag extractor - the update fuzzer has generated more egraphs that trigger failure
The improved random egraph generation now generates egraphs that cause the faster-greedy-dag extractor to fail. |
…s that are more likely to be problematic
@oflatt were your change requests addressed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! Looks great to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! A few organizational changes:
This generates some semi-random egraphs, runs extractors on them, checks that the extractions are valid, then checks that
the optimal extractions all have the same cost, and then checks that there are no extractions cheaper than the optimal extractions.
I'm happy to improve this. I've not done automated testing in Rust before, so it's easy for me to believe there are better ways.