-
Notifications
You must be signed in to change notification settings - Fork 13k
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 7 pull requests #111001
Rollup of 7 pull requests #111001
Conversation
…m_handling` `tests/run-make/alloc-no-oom-handling` tests that `alloc` under `no_global_oom_handling` builds and is warning-free. Do the same for `core` to prevent issues such as [1]. Link: rust-lang#110649 [1] Signed-off-by: Miguel Ojeda <[email protected]>
Fixes rust-lang#35785 by converting non UTF-8 linker output to Unicode using the OEM code page. Before: ```text = note: Non-UTF-8 output: LINK : fatal error LNK1181: cannot open input file \'m\x84rchenhaft.obj\'\r\n ``` After: ```text = note: LINK : fatal error LNK1181: cannot open input file 'märchenhaft.obj' ``` The difference is more dramatic if using a non-ascii language pack for Visual Studio.
I wrote these in a previous PR that I ended up withdrawing, so might as well submit them separately.
…kingjubilee Fix Unreadable non-UTF-8 output on localized MSVC Fixes rust-lang#35785 by converting non UTF-8 linker output to Unicode using the OEM code page. Before: ```text = note: Non-UTF-8 output: LINK : fatal error LNK1181: cannot open input file \'m\x84rchenhaft.obj\'\r\n ``` After: ```text = note: LINK : fatal error LNK1181: cannot open input file 'märchenhaft.obj' ``` The difference is more dramatic if using a non-ascii language pack for Windows.
…test, r=Mark-Simulacrum Add test for warning-free builds of `core` under `no_global_oom_handling` `tests/run-make/alloc-no-oom-handling` tests that `alloc` under `no_global_oom_handling` builds and is warning-free. Do the same for `core` to prevent issues such as [1]. Link: rust-lang#110649 [1]
…tic-note, r=compiler-errors improve error notes for packed struct reference diagnostic Addresses rust-lang#110199
Move most rustdoc-ui tests into subdirectories This makes it easier to know where to add a new test, and makes the top-level directory less overwhelming.
…riddle rustdoc: Get `repr` information through `AdtDef` for foreign items As suggested by `@notriddle,` this approach works too. The only downside is that the display of the original attribute isn't kept, but I think it's an acceptable downside. r? `@notriddle`
…ompiler-errors Do not resolve anonymous lifetimes in consts to be static. Fixes rust-lang#110931
…e8472 Improve internal field comments on `slice::Iter(Mut)` I wrote these in a previous PR that I ended up withdrawing, so might as well submit them separately. `@bors` rollup=always
@bors r+ rollup=never p=7 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: f5adff6bd8 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (d3edfd1): 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.
CyclesResultsThis 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.
|
Successful merges:
core
underno_global_oom_handling
#110652 (Add test for warning-free builds ofcore
underno_global_oom_handling
)repr
information throughAdtDef
for foreign items #110983 (rustdoc: Getrepr
information throughAdtDef
for foreign items)slice::Iter(Mut)
#110997 (Improve internal field comments onslice::Iter(Mut)
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup