chore(cli/bundle): make null-ctx dispatcher panic explicit#292
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
1 participant
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.
Description
The bundle dispatcher's opaque ctx slot is
?*anyopaquefor ABI symmetry with the runner, but every cli call path sets it before invoking. The cast helper usedctx.?, so a future site that wires the dispatcher without going throughrunDispatcher/cleanupDispatcherwould crash with a bare "safety unreachable" panic instead of a message that names the contract that was broken.This swaps the unwrap for
orelse @panicwith a wiring-bug message. Behaviour is unchanged on every current call path - the panic is reachable only from a misuse that today's code cannot produce. Release binary is byte-identical.Related Issue
Notes for Reviewers