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.

Sign up for GitHub

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

Jump to bottom

Use of isImmediatelyUnexplored in inappropriate places. #111

Open
BenSpencer opened this issue Jun 2, 2014 · 0 comments
Open

Use of isImmediatelyUnexplored in inappropriate places. #111

BenSpencer opened this issue Jun 2, 2014 · 0 comments
Assignees
@BenSpencer

Comments

@BenSpencer
Copy link
Contributor

Our utility function isImmediatelyUnexplored returns true for nodes of types TraceUnexplored, TraceUnexploredUnsat, TraceUnexploredUnsolvable and TraceUnexploredMissed. In some places where this is used, we only really want to test if the node in question is exactly Traceunexplored.

I have added a new utility function to test this, but I have not gone through the existing uses and seeing which ones are wrong.
@BenSpencer BenSpencer self-assigned this Jun 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BenSpencer BenSpencer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BenSpencer