Rollup of 10 pull requests #80178
Rollup of 10 pull requests #80178
Conversation
This commit modifies the `check_attr` pass so that attribute placement on generic parameters is checked for validity. Signed-off-by: David Wood <david@davidtw.co>
Add missing punctuation.
rustc_lint and rustc_lint_defs weren't switched because they're included in the compiler book and so can't use intra-doc links.
Stabilize or_insert_with_key Stabilizes the `or_insert_with_key` feature from rust-lang#71024. This allows inserting key-derived values when a `HashMap`/`BTreeMap` entry is vacant. The difference between this and `.or_insert_with(|| ... )` is that this provides a reference to the key to the closure after it is moved with `.entry(key_being_moved)`, avoiding the need to copy or clone the key.
…ttrs, r=lcnr passes: prohibit invalid attrs on generic params Fixes rust-lang#78957. This PR modifies the `check_attr` pass so that attribute placement on generic parameters is checked for validity. r? `@lcnr`
…k-Simulacrum Add the "async" and "promise" doc aliases to `core::future::Future` Adds the "async" and "promise" doc aliases to `core::future::Future`. This enables people who search for "async" or "promise" to find `Future`, which is Rust's core primitive for async programming. Thanks!
Switch some links in compiler/ to intra-doc links
Add `&mut` as an alias for 'reference' primitive Closes rust-lang#46075.
or_patterns: implement :pat edition-specific behavior cc rust-lang#54883 `@joshtriplett` This PR implements the edition-specific behavior of `:pat` wrt or-patterns, as determined by the crater runs and T-lang consensus in rust-lang#54883 (comment). I believe this can unblock stabilization of or_patterns. r? `@petrochenkov`
docs: Edit rustc_ast::token::Token Add missing punctuation.
…tebank Suppress `CONST_ITEM_MUTATION` lint if a dereference occurs anywhere Fixes rust-lang#79971
…s-schievink Fix typo
…lcnr Make BoundRegion have a kind of BoungRegionKind Split from rust-lang#76814 Also includes making `replace_escaping_bound_vars` only return `T` Going to r? `@lcnr` Feel free to reassign
|
@bors r+ rollup=never p=5 |
|
📌 Commit 8890048 has been approved by |
bors
added
the
S-waiting-on-bors
|
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message |
bors
added
S-waiting-on-author
|
☔ The latest upstream changes (presumably #77035) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
Successful merges:
core::future::Future)&mutas an alias for 'reference' primitive #80068 (Add&mutas an alias for 'reference' primitive)CONST_ITEM_MUTATIONlint if a dereference occurs anywhere #80133 (SuppressCONST_ITEM_MUTATIONlint if a dereference occurs anywhere)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup