-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
[package management] Add implicit dependency support to move compiler #21383
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
ebbc1fa
to
873cafe
Compare
873cafe
to
36d4c12
Compare
36d4c12
to
3405db6
Compare
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.
Overall the changes look good to me. I think I'm fine with this as-is, but in the future we probably will want to revisit how explicit deps are handled w.r.t. implicit deps and have these behave more like package overrides today (or at least it's possibly something that we should discuss sometime).
// implicits deps should be skipped if the manifest contains any of them | ||
// explicitly (or if the manifest is for a system package). | ||
let add_implicits: bool = !self.implicit_deps.iter().any(|(name, _)| { | ||
root_manifest.dependencies.contains_key(name) || root_manifest.package.name == *name |
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 we require the override = true
be set here? May help us out in the future possibly (and also makes it clear that an override is happening here).
Description
This PR adds support for implicit dependencies on the move side.
PR stack
#21204 Add implicit Sui dependencies
#21384 Refactors to BuildConfig
#21383 Add support for implicits to move package management
This also depends on @stefan-mysten 's ongoing tree-shaking work in #21356
Test plan
See
test_sources/implicits/README.md
for a description of the new snapshot testsRelease notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.