Stabilize atomic_try_updateand deprecate fetch_update starting 1.99.0#148590
Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom Feb 7, 2026
Merged
Stabilize atomic_try_updateand deprecate fetch_update starting 1.99.0#148590rust-bors[bot] merged 1 commit intorust-lang:mainfrom
atomic_try_updateand deprecate fetch_update starting 1.99.0#148590rust-bors[bot] merged 1 commit intorust-lang:mainfrom
Conversation
rustbot
added
S-waiting-on-author
5 tasks
Contributor
|
I would suggest splitting out the lint change into a separate PR. It would be useful even before stabilization, I don't think it requires its own FCP, and it'll make the API stabilization itself a bit easier to review. That's especially important since the simultaneous deprecation makes it a big and tricky diff by stabilization standards! |
GrigorenkoPV
force-pushed
the
atomic_try_update
branch
from
02e586c to
67b2e92
Compare
Contributor
Author
|
Good idea! Done: #148601 |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this pull request
Nov 8, 2025
…ng, r=Kivooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang#148590 Tracking issue for `update` and `try_update`: rust-lang#135894
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this pull request
Nov 8, 2025
…ng, r=Kivooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang#148590 Tracking issue for `update` and `try_update`: rust-lang#135894
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Nov 9, 2025
…ng, r=Kivooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang#148590 Tracking issue for `update` and `try_update`: rust-lang#135894
rust-timer
added a commit
that referenced
this pull request
Nov 9, 2025
GrigorenkoPV
force-pushed
the
atomic_try_update
branch
from
67b2e92 to
7ffe34e
Compare
github-actions bot
pushed a commit
to rust-lang/miri
that referenced
this pull request
Nov 10, 2025
…ooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang/rust#148590 Tracking issue for `update` and `try_update`: rust-lang/rust#135894
makai410
pushed a commit
to makai410/rustc_public
that referenced
this pull request
Nov 10, 2025
…ooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang/rust#148590 Tracking issue for `update` and `try_update`: rust-lang/rust#135894
makai410
pushed a commit
to makai410/rust
that referenced
this pull request
Nov 10, 2025
…ng, r=Kivooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang#148590 Tracking issue for `update` and `try_update`: rust-lang#135894
makai410
pushed a commit
to makai410/rustc_public
that referenced
this pull request
Nov 16, 2025
…ooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang/rust#148590 Tracking issue for `update` and `try_update`: rust-lang/rust#135894
Collaborator
|
☔ The latest upstream changes (presumably #149222) made this pull request unmergeable. Please resolve the merge conflicts. |
GrigorenkoPV
force-pushed
the
atomic_try_update
branch
from
7ffe34e to
9a0eb78
Compare
This comment has been minimized.
This comment has been minimized.
GrigorenkoPV
force-pushed
the
atomic_try_update
branch
from
9a0eb78 to
0733988
Compare
rustbot
added
the
S-waiting-on-review
rustbot
removed
the
S-waiting-on-author
Collaborator
This comment has been minimized.
This comment has been minimized.
Contributor
Author
|
@rustbot label -S-waiting-on-FCP RIP |
GrigorenkoPV
force-pushed
the
atomic_try_update
branch
from
0733988 to
65e453c
Compare
and deprecate fetch_update starting 1.99.0
GrigorenkoPV
force-pushed
the
atomic_try_update
branch
from
65e453c to
3a48b9f
Compare
Collaborator
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
GrigorenkoPV
changed the title
atomic_try_updateand deprecate fetch_update starting 1.96.0atomic_try_updateand deprecate fetch_update starting 1.99.0
Member
|
@bors r+ |
Contributor
rust-bors
bot
added
S-waiting-on-bors
jhpratt
added a commit
to jhpratt/rust
that referenced
this pull request
Feb 7, 2026
…jhpratt Stabilize `atomic_try_update`and deprecate `fetch_update` starting 1.99.0 Tracking issue: rust-lang#135894 FCP completed: rust-lang#135894 (comment) ~1.96.0 was chosen because I don't think the remaining month until 1.93.0 becomes beta is enough for the FCP to finish and this to get merged, so 1.94.0 + a couple of versions of leeway: rust-lang#135894 (comment) 1.99 suggested in rust-lang#148590 (comment) Closes rust-lang#135894
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Feb 7, 2026
…jhpratt Stabilize `atomic_try_update`and deprecate `fetch_update` starting 1.99.0 Tracking issue: rust-lang#135894 FCP completed: rust-lang#135894 (comment) ~1.96.0 was chosen because I don't think the remaining month until 1.93.0 becomes beta is enough for the FCP to finish and this to get merged, so 1.94.0 + a couple of versions of leeway: rust-lang#135894 (comment) 1.99 suggested in rust-lang#148590 (comment) Closes rust-lang#135894
This was referenced Feb 7, 2026
Contributor
|
⌛ Testing commit 3a48b9f with merge 83d71ef... Workflow: https://github.com/rust-lang/rust/actions/runs/21779822668 |
rust-bors bot
pushed a commit
that referenced
this pull request
Feb 7, 2026
Stabilize `atomic_try_update`and deprecate `fetch_update` starting 1.99.0 Tracking issue: #135894 FCP completed: #135894 (comment) ~1.96.0 was chosen because I don't think the remaining month until 1.93.0 becomes beta is enough for the FCP to finish and this to get merged, so 1.94.0 + a couple of versions of leeway: #135894 (comment) 1.99 suggested in #148590 (comment) Closes #135894
Contributor
|
@bors yield |
Contributor
|
Auto build cancelled. Cancelled workflows: The next pull request likely to be tested is #152282. |
rust-bors bot
pushed a commit
that referenced
this pull request
Feb 7, 2026
…uwer Rollup of 8 pull requests Successful merges: - #148590 (Stabilize `atomic_try_update`and deprecate `fetch_update` starting 1.99.0) - #150522 (Stabilize new inclusive range type and iterator type) - #152235 (Convert to inline diagnostics in `rustc_parse`) - #152267 (feat: Implement `int_from_ascii` for `NonZero<T>`) - #151576 (Stabilize `core::hint::cold_path`) - #151933 (Linker-plugin-based LTO: give an explanation how to use linker-plugin-lto with full LTO) - #152010 (Ignore all debuginfo tests for LLDB that we do not run in CI) - #152199 (Move `rustc_query_system::cache`.)
rust-timer
added a commit
that referenced
this pull request
Feb 7, 2026
Rollup merge of #148590 - GrigorenkoPV:atomic_try_update, r=jhpratt Stabilize `atomic_try_update`and deprecate `fetch_update` starting 1.99.0 Tracking issue: #135894 FCP completed: #135894 (comment) ~1.96.0 was chosen because I don't think the remaining month until 1.93.0 becomes beta is enough for the FCP to finish and this to get merged, so 1.94.0 + a couple of versions of leeway: #135894 (comment) 1.99 suggested in #148590 (comment) Closes #135894
yhdengh
added a commit
to fix-project/arca
that referenced
this pull request
Feb 27, 2026
- Rename `bigint_helper_methods` feature gate to `widening_mul` in `kernel/src/lib.rs` [rust-lang/rust#152018](rust-lang/rust#152018) - Remove stabilized `atomic_try_update` feature gate from `common/src/lib.rs` [rust-lang/rust#148590](rust-lang/rust#148590) --------- Co-authored-by: Yuhan Deng <yhdeng@stanford.edu>
makai410
pushed a commit
to makai410/rustc_public
that referenced
this pull request
Mar 27, 2026
…ooeo `invalid_atomic_ordering`: also lint `update` & `try_update` Split from rust-lang/rust#148590 Tracking issue for `update` and `try_update`: rust-lang/rust#135894
BoxyUwU
added
the
relnotes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
View all comments
Tracking issue: #135894
FCP completed: #135894 (comment)
1.96.0 was chosen because I don't think the remaining month until 1.93.0 becomes beta is enough for the FCP to finish and this to get merged, so 1.94.0 + a couple of versions of leeway: #135894 (comment)1.99 suggested in #148590 (comment)
Closes #135894