-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
cargo locate-project --workspace
loads all the workspace
#15107
Comments
Could you elaborate a bit on performance data you're looking for, and the scenario? It seems to me in a workspace of 400+ members (aws-sdk-rust) it takes ~150ms. Not ideal but it would be better to understand the use cases. |
@weihanglo I sometimes work on a workspace with ~1500 members (not open source sadly), and in this case, it takes most of the time more than a second. |
|
Hmmm interesting. Maybe adding a flag |
imo if this command is just about locating the workspace, I think its reasonable to skip validation. Other commands will need to be run and those can do that validation. We could punt on proper plumbing commands which would require doing the minimal work. I don't think its a big loss to this command to do it now. |
This sounds pretty reasonable. I went ahead and marked this as accepted. |
Problem
cargo locate-project --workspace
loads all the workspace instead of just returning the path of the workspace root.Steps
cargo locate-project --workspace
Possible Solution(s)
Instead of doing
src/bin/cargo/commands/locate_project.rs
I think that
or something like that would be better. Because when in a big workspace with a lot of members in a workspace, it will load some unused data.
The text was updated successfully, but these errors were encountered: