-
Notifications
You must be signed in to change notification settings - Fork 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
feat: isolate DefId
: faster build times
#703
Conversation
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.
💯 for fewer dependencies, esp. this one. But I'm not sure if it actually works.
Do we need to publish this one? I don't see it anywhere in publishing.md. But I'm not sure if you can publish a crate with a path
attribute.
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.
Can you update the publish.md to make sure have all the crates in there that we need (and also mentions the ones we don't so that we know that didn't just forget one)?
If we don't need to publish this one, it looks good to me.
… w/o `full` This get rids of the `#[path]` introduced #703 by using the disabling the new `full` feature of `hax-frontend-exporter`.
… w/o `full` This get rids of the `#[path]` introduced #703 by using the disabling the new `full` feature of `hax-frontend-exporter`.
… w/o `full` This get rids of the `#[path]` introduced #703 by using the disabling the new `full` feature of `hax-frontend-exporter`.
The OCaml build depends on the binary
hax-engine-names-extract
, which, at build-time, depends on the hax frontend.hax-engine-names-extract
runs the frontend at build time onhax-engine-names
, which itself used to depend on the cratehax-engine-frontend
. Running hax however sets specific cfg flags, yielding recompilations.This PR cut the dependency between
hax-engine-names
andhax-engine-frontend
.hax-engine-names
needs only three type definitions fromhax-engine-frontend
: this PR isolates those three types in a module, and makeshax-engine-names
directly use that module, inlined.