regression: `Atomic` is ambiguous

[BoxyUwU]

• https://crater-reports.s3.amazonaws.com/beta-1.88-1/beta-2025-05-26/gh/astral4.phf-bench/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.88-1/beta-2025-05-26/gh/RagnarGrootKoerkamp.cacheline-ef/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.88-1/beta-2025-05-26/reg/compressed-intvec-0.3.1/log.txt
• and a bunch more occurances in the rustdoc crater run

[INFO] [stdout] error[E0659]: `Atomic` is ambiguous
[INFO] [stdout]     --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/common_traits-0.11.2/src/impls.rs:1506:14
[INFO] [stdout]      |
[INFO] [stdout] 1506 |         impl Atomic for $aty {
[INFO] [stdout]      |              ^^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of multiple glob imports of a name in the same module

[bjorn3]

This is caused by a blanket import of core::sync::atomic::* importing the new std::sync::atomic::Atomic type, while at the same time having a blanket impl of crate::* for an Atomic trait.

[zachs18]

Looks like the root affected crate common_traits was fixed upstream in 0.11.3 (published April 30) zommiommy/common_traits#3 zommiommy/common_traits@968661e but these were compiled against 0.11.2

[zommiommy]

I confirm, I pushed a new version that avoids glob imports altogether.

[cuviper]

New public items are considered minor breaking changes due to potential glob ambiguity. In this case, given that the root affected crate has a published fix, I think we can just close.