-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Explain that ? converts the error type using From #60924
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
FWIW, I'm experimenting with using |
@cuviper the regression on error messages should make it obvious when hacks like this are in use. I believe the weird error you note in that PR is partly one of these cases. |
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.
Awesome! Thank you Esteban! ❤️
Scheduled a try build for crater. |
@bors r+ rollup |
📌 Commit 65b7319 has been approved by |
Explain that ? converts the error type using From Fix rust-lang#60917.
Rollup of 8 pull requests Successful merges: - #60370 (Mark core::alloc::Layout::from_size_align_unchecked const) - #60678 (Stabilize vecdeque_rotate) - #60924 (Explain that ? converts the error type using From) - #60931 (Use iter() for iterating arrays by slice) - #60934 (Declare DefIndex with the newtype_index macro) - #60943 (fix copy-paste typo in docs for ptr::read_volatile) - #60945 (Simplify BufRead::fill_buf doc example using NLL) - #60947 (Fix typos in docs of GlobalAlloc) Failed merges: r? @ghost
☔ The latest upstream changes (presumably #60949) made this pull request unmergeable. Please resolve the merge conflicts. |
Bors was able to merge this even though it was unmergeable? |
The rollup #60949 contains this PR. |
Fix #60917.