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

smbc returns model with empty type even though a val of this type was declared #5

Closed
samuelgruetter opened this issue Oct 13, 2018 · 6 comments
Assignees
Labels

Comments

@samuelgruetter
Copy link

Description of problem: see here.

@c-cube c-cube self-assigned this Oct 13, 2018
@c-cube c-cube added the bug label Oct 13, 2018
@c-cube
Copy link
Owner

c-cube commented Oct 13, 2018

I'll take a look, thank you.

@c-cube c-cube closed this as completed in 4e10681 Oct 13, 2018
@c-cube
Copy link
Owner

c-cube commented Oct 13, 2018

Empty types will always be completed now. It never hurts to do that.

@samuelgruetter
Copy link
Author

Empty types will always be completed now. It never hurts to do that.

Even if I have axiom forall (v: MyEmptyType). false. ?

@c-cube
Copy link
Owner

c-cube commented Oct 13, 2018

Hmmm I'd consider that as unsat, but that's an interesting point. I suppose exists (v:foo). true would be used to make a type non empty? I'm not used to reasoning with possibly empty types, tbh.

(cc @blanchette for opinions on the topic)

@blanchette
Copy link
Collaborator

blanchette commented Oct 17, 2018 via email

@c-cube
Copy link
Owner

c-cube commented Oct 17, 2018

@blanchette yes, datatypes are always inhabited. Uninterpreted types are, too, but this bug occurs in the case where a type is never touched (no value in it is ever used), so the printed model was empty :-)
I guess that's the way things should continue to be, then. Thank you.

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

No branches or pull requests

3 participants