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

"set" quantification is allowed in syntax, but meaning isn't preserved #147

Open
tnelson opened this issue Apr 29, 2022 · 0 comments
Open

Comments

@tnelson
Copy link
Owner

tnelson commented Apr 29, 2022

sig A {}
test expect {
    higherOrderSome: {
        some X: set A | #X > 1
    } is sat
}

The above parses and runs without any error -- until the test fails. If we're going to permit Alloy-style higher-order some we need to preserve its semantics. Alternatively, we could give an error when someone tries to use Alloy-style some ... set ....

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

No branches or pull requests

1 participant