Repository navigation
Support positional variadic task arguments. - #19
Merged
samuel-williams-shopify merged 1 commit intoOct 5, 2026
Merged
Conversation
samuel-williams-shopify
deleted the
feature/positional-variadic-arguments
branch
October 5, 2026 08:49
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.
Allow task authors to define a
Vec<T>as an unbounded positional argument list. This lets project commands accept natural argument lists such ascargo bake markdown:normalize **/*.md.Previously,
Vec<T>parameters were only available as repeatable named options. The new#[bake(positional)]annotation makes bare values fill aVec<T>through the end of that task invocation. Since the parser cannot infer whether a later bare value is another task or another list item, callers use::to start the next task. Named options remain usable alongside the positional list.The macro validates the annotation and requires the variadic parameter to be the final positional parameter. Task help and author documentation describe the new syntax and chaining rule.