-
Notifications
You must be signed in to change notification settings - Fork 22
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
CLI: F*: interfaces
flag is a bit too expressive
#397
Labels
Comments
This will be closed when #465 is done |
W95Psp
added a commit
that referenced
this issue
Jan 29, 2024
W95Psp
added a commit
that referenced
this issue
Jan 29, 2024
W95Psp
added a commit
that referenced
this issue
Jan 29, 2024
W95Psp
added a commit
that referenced
this issue
Jan 30, 2024
W95Psp
added a commit
that referenced
this issue
Jan 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hax into fstar --interfaces
andhax into --include_namespaces
accept the same kind of value (they share a same type and parser).With the latter, the user can either:
-
);+
);+!
).The former accepts the same grammar, but
+!
makes no sense: either we extract an interface for a module, or we don't, but there is no third option.Here, either the Rust type
InclusionClause
should be made polymorphic to allow or not+!
, or we should have a different type.The text was updated successfully, but these errors were encountered: