Create a JobSplitter to Increase Flexibility of Statement Parsing
We are currently limited when processing commands like the following:
true && let a = 5
What happens is that the entire pipeline is considered as a command, and each job in the pipeline is executed as a command. Let is not a command though, so this will fail. This would require some more advanced restructuring, though, so it won't be easy. We'd have to add a job splitter to split statements into jobs, and make a number of possible changes within pipeline execution to account for jobs possibly being keywords.