You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: resources/deliberate-ub.md
+2
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,8 @@ We should evaluate whether there truly is some use-case here that is not current
19
19
see the [discussion here](https://github.com/rust-lang/unsafe-code-guidelines/issues/449).<br>
20
20
The alternative is to not use the "fast path" for problematic types (and fall back to the SeqLock), but that requires some way to query at `const`-time whether the type contains padding (or provenance).
21
21
(Or of course one can use inline assembly, but it would be better if that was not required.)
22
+
* tokio causes race conditions between atomic and non-atomic loads which are [not permitted](https://doc.rust-lang.org/nightly/std/sync/atomic/index.html#memory-model-for-atomic-accesses);
23
+
see [this issue](https://github.com/tokio-rs/tokio/issues/6155) for details.
0 commit comments