docs(allocator): update docs with why Ordering::SeqCst is required#22086
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Merging this PR will not alter performance
Comparing Footnotes
|
There was a problem hiding this comment.
Pull request overview
Docs-only update clarifying the rationale behind using Ordering::SeqCst when toggling is_double_owned during allocator deallocation coordination between Rust Drop and the JS GC finalizer.
Changes:
- Replaced the prior “not sure, using SeqCst to be safe” note with a more explicit explanation of the intended concurrency correctness requirements around
is_double_owned.

Docs-only change. Update doc comment for
FixedSizeAllocatorPoolto explain whyOrdering::SeqCstis necessary when checking if an arena chunk is double-owned or not during eitherDropon Rust side, or GC on JS side.