-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Considers crates of workspace projects #11270
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
} | ||
}; | ||
eprintln!("cargo_config_build_target for {:?} yields a target of {:?}", cargo_toml, r); | ||
r |
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'll remove this line ultimately
None => bail!("no projects"), | ||
Some(it) => it, | ||
Some(it) => it.clone(), |
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.
It is now possible to have more than one project. However, we can now rely on the last project returned being the outermost one.
} | ||
eprintln!("DISCOVERED: {:?}", manifests); |
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.
This line will go.
@@ -137,7 +141,7 @@ impl ProjectManifest { | |||
.collect::<FxHashSet<_>>() | |||
.into_iter() | |||
.collect::<Vec<_>>(); | |||
res.sort(); | |||
res.sort_by(|a, b| b.cmp(a)); |
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.
Performs a reverse sort so that the inner most ones are returned first.
Closing given #11268 (comment) |
Background info: #11268
This is presently yielding the following during discovery:
...which looks right.
Then, later on, the targets appear to be resolved correctly:
...however, when applying to my project I'm not seeing that
interrupt::take!
macro resolved correctly still. More digging required.