refactor: clarify waiter arena contracts - #191
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SlotId, removing manual encode/decode calls and the associated unsafe constructionWaitSetentry with the non-CopyWakerToken, and useslot/tokenconsistently through its callersnext_vacantas the field namepubinside that module boundaryArenaValuesbehind owning iterators fromArena::take_allandWaitSet::take_wakersrepr(transparent)layout guarantees on internal wrappersThe existing module-level
allow(dead_code)remains intentionally simple:WaitListandWaitSetuse different subsets of the arena API, so single-primitive feature builds inevitably leave part of it unused.Small-vector decision
ArenaValuesis the safe, specialized equivalent of the small-vector behavior needed here: keep one value inline, store only additional values in aVec, and consume the values through iteration. I evaluated vendoring SmallVec 1.15.2, but its general implementation and unsafe storage machinery are disproportionate to these three operations. This keeps the focused representation without adding a production dependency or vendored third-party surface.Validation
cargo +1.86.0 check --package asyncband --all-features --testscargo test --workspace --all-featurescargo run -p x -- checkcargo run -p x -- lint