Variable expansion and subshells, add Vec<Arg> for commands #6
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.
Add Support for Subshells + Variable Expansion
cmd1 (cmd2)
andcmd1 $(cmd2)
$name
but not `${name}Option<Token>
,Lexer::lex_subshell
returns aResult<Token>
so that unmatched parentheses can be collected as errors to emitCommand::argv
from aVec<String>
to aVec<Arg>
whereArg
is an enum with variants for basic "words", subshells, and variables.Remove redundant CommandGroup
and_then
field of theCommand
struct, thecommands
inCommandGroup
was redundant.AndThen
now has to have aBox<Command>
Update Tests
Vec<Arg>
format forCommand
.