-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 5 pull requests #102691
Rollup of 5 pull requests #102691
Conversation
Since 76a3b60 converted code headers to real headers, `display: block` is now the default.
modified: compiler/rustc_trait_selection/src/traits/error_reporting/mod.rs modified: src/test/ui/error-codes/E0283.stderr modified: src/test/ui/error-codes/E0790.stderr modified: src/test/ui/traits/static-method-generic-inference.stderr modified: src/test/ui/type/issue-101866.stderr
The rls stub is a simple stable tool, which doesn't need compiler libs.
…th_hasher, r=oli-obk,fee1-dead Make Hash{Set,Map}::with_hasher unstably const Makes [`HashMap::with_hasher`](https://doc.rust-lang.org/stable/std/collections/hash_map/struct.HashMap.html#method.with_hasher) and [`HashSet::with_hasher`](https://doc.rust-lang.org/stable/std/collections/hash_set/struct.HashSet.html#method.with_hasher) `const`. This allows ```rust static GlobalState: Mutex<HashMap<i32, i32, SomeHasher>> = Mutex::new(HashMap::with_hasher(SomeHasher::new())) ``` Tracking issue: rust-lang#102575
…rn-for-returning-function-error, r=compiler-errors Slightly improve no return for returning function error Fixes rust-lang#100607 The rationale is that absolute beginners will be slightly confused as to why certain lines of code in a function does not require a semicolon. (I have actually witness a beginner having this confusion). Hence, a slight rationale is added "to return this value", which signals to the user that after removing said semicolon the value is returned resolving that error. However, if this is not desirable, I welcome any other suggestions. Thanks.
…splay-block, r=GuillaumeGomez rustdoc: remove no-op CSS `.code-header { display: block }` Since 76a3b60 converted code headers to real headers, `display: block` is now the default.
…piler-errors follow-up fix about 101866 to print the self type. modified: compiler/rustc_trait_selection/src/traits/error_reporting/mod.rs modified: src/test/ui/error-codes/E0283.stderr modified: src/test/ui/error-codes/E0790.stderr modified: src/test/ui/traits/static-method-generic-inference.stderr modified: src/test/ui/type/issue-101866.stderr
Don't build the compiler before building rls The rls stub is a simple stable tool, which doesn't need compiler libs. (Similar to rust-lang#97511)
@bors r+ p=5 |
@bors rollup=never |
⌛ Testing commit 40ce4af with merge 4fd05acdedb8df2204d05e135c486961a8a75be8... |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: d8613f792c In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (dd8c3a8): 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. Footnotes |
Successful merges:
.code-header { display: block }
#102662 (rustdoc: remove no-op CSS.code-header { display: block }
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup