rjmholt

3 ms·

1. 1.▲
   by rjmholt 7y ago

   In my RFC I dubbed them (&& and ||) the pipeline chain operators because you use them to chain syntactic pipelines together conditionally. The POSIX shell spec calls them AND-OR lists, which I didn’t think was as descriptive. To e
2. 2.▲
   by rjmholt 7y ago

   (Sorry for the late response. Currently on vacation without a laptop.) I wasn’t on the team when that change was made but I think it was discussed in [0]. I’m not certain, but I suspect the reasoning went that a new name was needed to not c
3. 3.▲
   by rjmholt 7y ago

   Oh, this is my PR! Also worth taking a look at the RFC[0] and the original issue[1]. Just to address some questions in the comments: These operators had no equivalent in PowerShell previously, but they’d always been planned from the outset.