-
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
Charon traits merge #553
Charon traits merge #553
Conversation
cfd1e70
to
c25761c
Compare
c25761c
to
99ca4ac
Compare
e11cbe9
to
a515aef
Compare
b0802bb
to
44b259d
Compare
b92c568
to
5ce94c4
Compare
Some of the structure of the type that are used in the THIR/MIR AST changed, thus some hashes changed as well.
On my side, I'm OK with the changes introduced in this PR. @franziskuskiefer, I'm postponing tests on MIR to #481: I have no time for that, and this PR has been waiting for too long, Son needs it. However, I think we need to have #481 as soon as possible: let's plan that next Thursday at CC. EDIT: seems like there is a regression. When extracting curve25519 from the specs repo, the frontend seemlingly produces unsafe blocks... |
The ImplExpr resolution was calling into `mir` helpers, which is failing on some test. We don't use this information in hax for THIR, so I'm just dropping that info for now.
Hax relies on span equality for uninlining macro calls, this was broken since there is no way to recover `rust_span_data` when parsing it back from the engine.
02a88b9
to
0274953
Compare
Todo list:
[ ] Add tests for MIR extraction in hax: see CI: test the frontend (THIR+MIR) on a list of given crate #481[ ] Check if the changes are fine in charon: this will be done in follow up PRS