-
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
Expand error message to explain that a string was found #8235
Expand error message to explain that a string was found #8235
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
may be we should write quotes also |
I would agree yeah it probably makes the most sense to also include the surrounding quotes, but otherwise looks great to me! |
With `opt-level = "3"` this previously said: must be an integer, `z`, or `s`, but found: 3 for ... The error message doesn't make that super clear. This should now be a bit more clear. Fixes rust-lang#8234
05a6127
to
09084a3
Compare
Adjusted and also fixed the tests. |
Now they fail in |
@bors: r+ |
📌 Commit 09084a3 has been approved by |
⌛ Testing commit 09084a3 with merge db702d3d09de4c1c1284e159090f49b793a7fe4d... |
💔 Test failed - checks-azure |
☀️ Test successful - checks-azure |
Update cargo 9 commits in cb06cb2696df2567ce06d1a39b1b40612a29f853..500b2bd01c958f5a33b6aa3f080bea015877b83c 2020-05-08 21:57:44 +0000 to 2020-05-18 17:12:54 +0000 - Handle LTO with an rlib/cdylib crate type (rust-lang/cargo#8254) - Gracefully handle errors during a build. (rust-lang/cargo#8247) - Update `im-rc` to 15.0.0 (rust-lang/cargo#8255) - Fix `cargo update` with unused patch. (rust-lang/cargo#8243) - Rephrased error message for disallowed sections in virtual workspace (rust-lang/cargo#8200) - Ignore broken console output in some situations. (rust-lang/cargo#8236) - Expand error message to explain that a string was found (rust-lang/cargo#8235) - Add context to some fs errors. (rust-lang/cargo#8232) - Move SipHasher to an isolated module. (rust-lang/cargo#8233)
With
opt-level = "3"
this previously said:The error message doesn't make that super clear.
This should now be a bit more clear.
Fixes #8234
We could even include a bit more saying that
"3"
should become 3 (either unconditionally or after trying to parse"3"
into an integer?cc @steveklabnik