re-enable extraction of results in SMTBackend.solve, fix examples #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Examples and tests were broken due to trivial changes to APIs (and
renaming of the crate from libsmt -> rustproof_libsmt).
One thing is that this reverts 'bug fix for hanging', which I think
was due to calling '(exit)' twice in the case of a Sat result from
solve(). I think the right thing to do is not call exit at all -- z3
will exit on its own if the write end of its stdin is closed
(returning EOF to z3), as should happen when the rust process exits,
and besides, we might want to iteratively invoke solve (with
appropriate push/pop context calls) on the same z3 instance.