6

Stabilize cfg_target_has_atomic by Amanieu · Pull Request #93824 · rust-lang/rus...

 2 years ago
source link: https://github.com/rust-lang/rust/pull/93824
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Conversation

Copy link

Contributor

Amanieu commented 8 days ago

edited by Mark-Simulacrum

target_has_atomic_equal_alignment is now tracked separately in #93822.

Partially touches on #32976 (maybe closes, but nominated to check on load_store being part of the stabilization)

Copy link

Collaborator

rust-highfive commented 8 days ago

r? @davidtwco

(rust-highfive has picked a reviewer for you, use r? to override)

This comment has been hidden.

Amanieu

force-pushed the stable_cfg_target_has_atomic

branch from c8c3dc0 to d469cce 8 days ago

Copy link

Member

davidtwco commented 7 days ago

Looks like you've already had an FCP for this in #32976 so I'll just go ahead and above.

@bors r+

Copy link

Contributor

bors commented 7 days ago

pushpin Commit 49d4823 has been approved by davidtwco

@@ -26,12 +26,10 @@ const GATED_CFGS: &[GatedCfg] = &[

// (name in cfg, feature, function to check if the feature is enabled)

(sym::target_abi, sym::cfg_target_abi, cfg_fn!(cfg_target_abi)),

(sym::target_thread_local, sym::cfg_target_thread_local, cfg_fn!(cfg_target_thread_local)),

(sym::target_has_atomic, sym::cfg_target_has_atomic, cfg_fn!(cfg_target_has_atomic)),

(sym::target_has_atomic_load_store, sym::cfg_target_has_atomic, cfg_fn!(cfg_target_has_atomic)),

Is it intentional that we're stabilizing load_store as well? My recollection of T-lang discussion was that we were intending to limit to just target_has_atomic on the first pass.

Copy link

Contributor

Author

Amanieu commented 7 days ago

I wasn't present in the lang meeting and assumed target_has_atomic_load_store would be stabilized as well since I haven't seen any comments saying otherwise.

OK -- I'm not sure either. I guess this is another point in favor of clear FCPs on long-lived tracking issues with little in the description. Let's not r- this to avoid canceling the rollup as well, and I can make sure that @rust-lang/lang puts this on its agenda on Tuesday next week to discuss whether to stabilize has_atomic_load_store as well.

Copy link

Contributor

nikomatsakis commented 7 days ago

Over at #32976, @joshtriplett wrote:

We'd like to confirm that we'll have documentation (in the Rust documentation for cfg) of exactly what this checks.

Do we, indeed, have documentation for this? Is there a stabilization report? I'm realizing I have no idea what is being stabilized here and why that subset was chosen.

bors

merged commit aa20959 into

rust-lang:master 7 days ago

20 checks passed

rustbot

added this to the 1.60.0 milestone

7 days ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Milestone

1.60.0

Linked issues

Successfully merging this pull request may close these issues.

None yet

8 participants

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK