Repository navigation
Clear stale extra arguments before parsing a new invocation - #177
Merged
inhere merged 1 commit intoOct 31, 2026
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.
Reusing a command can deliver extra arguments from its previous invocation. ParseArgs only replaces its remaining-argument slice when new extras exist, so an invocation with no extras can silently receive the old ones.
Reset that runtime slice at the start of each parse, retaining existing named-argument binding and validation behavior.
Go 1.26.0 / macOS arm64 validation:
old, empty,new, empty extras, instead ofold,old,new,new.Other bound flag/argument values and concurrent-command semantics are unchanged. Other supported Go/OS combinations remain unverified locally.