-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Rollup of 8 pull requests #106892
Rollup of 8 pull requests #106892
Conversation
As @bjorn3 pointed out [here], I used the wrong stability attribute in rust-lang#98368 when making `std::os::fd` public. I set it to Rust 1.63, which was when io-safety was stabilized, but it should be Rust 1.66, which was when `std::os::fd` was stabilized. [here]: rust-lang#98368 (comment)
Signed-off-by: Yuki Okushi <[email protected]>
Signed-off-by: Yuki Okushi <[email protected]>
suggested by Nilstrieb Co-authored-by: nils <[email protected]>
fix: misleading "add dyn keyword before derive macro" suggestion Fixes rust-lang#106071
Suggestion for type mismatch when we need a u8 but the programmer wrote a char literal Today Rust just points out that we have a char and we need a u8, but if I wrote 'A' then I could fix this by just writing b'A' instead. This code should detect the case where we're about to report a type mismatch of this kind, and the programmer wrote a char literal, and the char they wrote is ASCII, so therefore just prefixing b to make a byte literal will do what they meant. I have definitely written this mistake more than once, it's not difficult to figure out what to do, but the compiler might as well tell us anyway. I provided a test with two simple examples where the suggestion is appropriate, and one where it is not because the char literal is not ASCII, showing that the suggestion is only triggered in the former cases. I have contributed only a small typo doc fix before, so this is my first substantive rustc change.
…ilstrieb Remove various double spaces in compiler source comments. Was asked to do it by `@Nilstrieb`
…ation, r=notriddle Add explanation comment for GUI test r? `@notriddle`
…stable-version, r=m-ou-se Fix the stability attributes for `std::os::fd`. As `@bjorn3` pointed out [here], I used the wrong stability attribute in rust-lang#98368 when making `std::os::fd` public. I set it to Rust 1.63, which was when io-safety was stabilized, but it should be Rust 1.66, which was when `std::os::fd` was stabilized. [here]: rust-lang#98368 (comment)
…errors Add regression test for rust-lang#92157 Closes rust-lang#92157 r? compiler-errors Signed-off-by: Yuki Okushi <[email protected]>
…errors Add regression test for rust-lang#42114 Closes rust-lang#42114 r? compiler-errors Signed-off-by: Yuki Okushi <[email protected]>
…iper doc: fix typo
@bors r+ rollup=never p=8 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: afaf3e07aa In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (754f6d4): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
Successful merges:
std::os::fd
. #106867 (Fix the stability attributes forstd::os::fd
.)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup