J. S. Choi

> @littledan: I take it that, if we go down the Hack-style path, we're not trying for any kind of path for the placeholder to be subsumed by @rbuckton's partial...

In https://github.com/tc39/proposal-pipeline-operator/issues/84#issuecomment-363454642 I used a `##` nullary operator as a pipe placeholder. It looks nice and it doesn’t mess up GitHub’s current JavaScript syntax highlighting, but it probably would be...

Ah, `$_` brings back dormant memories of Perl… For what it’s worth, [Perl 6 actually turns Perl 5’s `$_` into an impressively unified concept of a lexical “topic variable”](https://docs.perl6.org/language/variables#The_$__Variable), which...

There is also Safari Web Inspector’s use of `$1`, `$2`, … to denote previously evaluated expressions in its console REPL, I suppose. I used to be very against using a...

@bisouduperou: I agree that too much context sensitivity is undesirable. I am not a big fan of shadowing `$`; I might want to use an outer `$` in a pipeline’s...

In light of some possible confusion that has occurred around the phrase “Hack style” (Proposal 2 only versus Proposals 2,3,4), I’m renaming this issue. I may do the same in...

I just realized that the [`|?>` example in the explainer](https://github.com/tc39/proposal-pipeline-operator/blob/main/README.md#optional-hack-pipes) doesn’t short-circuit. I meant for it to short-circuit, and I’ll fix that later.

> @tht13: Another solution to this problem which I have considered is a Electron version controller which installs global versions of Electron for the system to share, so if two...

I am mildly on the side of including ordinal/counter integers in `map`. > [@ljharb] To me this layout reinforces to me that there shouldn’t be one. Avoiding object allocations is...

@littledan I’ll write one. Edit: Dang, beaten to it.