-
Notifications
You must be signed in to change notification settings - Fork 1
(WIP)Support annotations for predicates #20
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
Conversation
Support logical connectives in annotations
Define rty::Formula and replace UnboundAssumption and Refinement with it
Introduce PlaceTypeBuilder to simplify PlaceType construction
Add documentation to annot, chc, and pretty modules
Add documentation to rty and some other modules
Add GitHub Actions workflow to host docs in GitHub pages
Handle parens in annotations properly
Ignore lifetime parameters properly when numbering type params
Register EnumDatatypeDef on-demand
Enable to parse enum constructors in annotations
Implement #[thrust::extern_spec_fn]
More annotation syntax
.tmp/rust.log
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that I accidentally included debug logs in my PR. Is it okay if I force push to completely remove those large files from the commit history?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, you are free to force push on your own branch
|
For now, I'll implement the parser to recognize a single-segment path followed by parenthesized arguments as a predicate call. (The current implementation already seems to recognize multi-segment paths as datatype constructor calls.) |
5834d64 to
2dc500f
Compare
|
I decided to split this implementations into separate two parts:
|
No description provided.