gh-bitflags/bitflags
Watch
1
0
Fork
You've already forked bitflags
 0
Code Issues 10 Pull requests Releases 53 Activity

Feature request: Atomic support #472

New issue
Open
opened 2026-02-11 08:28:14 -06:00 by fan2nd · 1 comment
fan2nd commented 2026-02-11 08:28:14 -06:00 (Migrated from github.com)

Inner atomic type support and Send + Sync.

Inner atomic type support and Send + Sync.
KodrAus commented 2026-02-13 16:06:10 -06:00 (Migrated from github.com)

See #420 and #391

This is something that's come up before, but we haven't added direct support for to try keep complexity down. The API for an atomic set of flags is entirely different to what bitflags currently offers. I would be interested in revisiting this though. Especially if we can come up with a scheme that still can support the regular bitflags API too.

See #420 and #391 This is something that's come up before, but we haven't added direct support for to try keep complexity down. The API for an atomic set of flags is entirely different to what `bitflags` currently offers. I would be interested in revisiting this though. Especially if we can come up with a scheme that still can support the regular `bitflags` API too.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release/1.x
2.13.2
2.13.1
2.13.0
2.12.1
2.12.0
2.11.1
2.11.0
2.10.0
2.9.4
2.9.3
2.9.2
2.9.1
2.9.0
2.8.0
2.7.0
2.6.0
2.5.0
2.4.2
2.4.1
2.4.0
2.3.3
2.3.2
2.3.1
2.3.0
2.2.1
2.2.0
2.1.0
2.0.2
2.0.1
2.0.0
2.0.0-rc.3
2.0.0-rc.2
2.0.0-rc.1
1.3.2
1.3.1
1.3.0
1.2.1
1.2.0
1.1.0
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
0.9.1
0.9.0
0.8.2
0.8.1
0.8.0
0.7.1
0.7.0
0.6.0
Labels
Clear labels   
bug

   
good first issue
No labels
bug
good first issue
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-bitflags/bitflags#472
No description provided.