-
Notifications
You must be signed in to change notification settings - Fork 993
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
Improve actionability of "resolver = 2" error #2217
Comments
The docs that explain how to "fix" this: https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions |
In regards to Rust 2021, I would like to note that it is somewhat misleading with respect to workspaces since you will need to specify (edit: that is when using a "virtual" manifest) |
If you don't want to include a more complete description in the error message, including a link could still provide a hint of where to find more details. Either to the URL @thechubbypanda suggested, to this issue, or whatever |
Some users aren't seeing this error at all: I'm not entirely sure why, and can't reproduce locally on Windows 10 :( |
Cargo added a warning when the resolver isn't explicitly specified in a workspace containing crates using newer editions: rust-lang/cargo#10910 Although, this probably doesn't completely address the issue since a user could still explicitly set |
This isn't going to be a problem anymore as we shouldn't require it as of v0.16.0 |
Bevy users have been getting an error that looks like:
This is not very actionable or accessible for new users. Ideally, this error could be made somewhat more verbose to explain how to do this (and mention that they could swap to Rust 2021 instead).
Motivated by bevyengine/bevy#3205
The text was updated successfully, but these errors were encountered: