Summary: See comments added in the code: there's always a chance some unsat states make it to the end of the execution of an instructions. Before this diff they would get propagated and executed until some code path actually bothers to check their satifiability. After this diff we throw them out at the end of the execution of the first instruction they get generated in. An alternative design would be to return Unsat explicitly everywhere we currently might return `false_`. This would be good too but there's still a chance we'd generate `false_` and so even if we did that more significant refactoring, the detection in this diff would still be a good last line of defense. Reviewed By: ezgicicek Differential Revision: D25336042 fbshipit-source-id: a24693596master
parent
e152ba8f33
commit
e526cf157a
Loading…
Reference in new issue