-
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
Rollup of 6 pull requests #84389
Rollup of 6 pull requests #84389
Conversation
…nnytm fix 'const-stable since' for NonZeroU*::new_unchecked For the unsigned `NonZero` types, `new_unchecked` was const-stable from the start with rust-lang#50808. Fix the docs to accurately reflect that. I think this `since` is also incorrect: ```rust #[stable(feature = "from_nonzero", since = "1.31.0")] impl From<$Ty> for $Int { ``` The signed nonzero types were only stabilized in 1.34, so that `From` impl certainly didn't exist before. But I had enough of digging through git histories after I figured out when `new_unchecked` became const-stable...^^
Document that `index` and `index_mut` can panic I thought this was noteworthy and I think a bit more explicitness does no harm.
…=jonas-schievink ⬆️ rust-analyzer
…trochenkov Improve the docstrings of the `Lto` struct. This change is the result of [this zulip discussion](https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/Making.20sense.20of.20LTO.20modes.20in.20rustc). Hopefully it makes things a little clearer. What do you think?
Fix broken doc link
…=jackh726 Add GAT related tests Closes rust-lang#79949 Closes rust-lang#79636 Closes rust-lang#78671 Closes rust-lang#70303 Closes rust-lang#70304 Closes rust-lang#71176
@bors r+ rollup=never p=5 |
📌 Commit f2b4d4c has been approved by |
⌛ Testing commit f2b4d4c with merge 8bd8c1ba9b372530cd937fc6e51e54993f257c99... |
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit f2b4d4c with merge d6270f13a1f6771287a33303866e778cb5825f0b... |
💔 Test failed - checks-actions |
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot)
|
@bors treeclosed=1000 This keeps happening:
Looking into it. |
Fix is being merged: #84394 Closing this rollup PR, since there's more rollup'able PRs waiting now. |
Successful merges:
index
andindex_mut
can panic #84301 (Document thatindex
andindex_mut
can panic)Lto
struct. #84365 (Improve the docstrings of theLto
struct.)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup