J. S. Choi

Yes, the assumption of this example was that F# pipes would have looser precedence than `=>`, in order to allow unparenthesized `input |> x => x + 1`. I would...

I think they’re referring to the copious use of bolding in the explainer document. That’s my fault; my apologies. It’s a habit I picked up from [Bret Victor in his...

Keep in mind the following paragraphs from the [explainer’s description](https://github.com/tc39/proposal-pipeline-operator/#description): > A pipe body must use its topic value at least once. For example, `value |> foo + 1` is...

> Ternary has [higher precedence](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Operator_Precedence) than assignment, I guess there should not be a problem with `a |> b ? % : c`. ~~I think this might be an error...

This is a little off topic, but the weirdness here is that `=` is not really a binary operator in the usual sense. It is a weird operator: it is...

I think we intend to ban `a ? b : c |> #` without parentheses and to force the developer to specify between `(a ? b : c) |> #`...

This seems fine to me so far. When you finish, I will re-review and merge. Thank you again for your help. 😄

Note: I may make some additions to the explainer file soon. I will avoid deletions and modifications of existing lines, so it should stay mergeable. Also, please mark this pull...

@benlesh: Hey, I appreciate your offer very much. (There are in fact several other early proposals that I, maybe in a few months, would love to have assistance with regards...

~~Yes, I only wish https://www.npmjs.com/browse/depended/rxjs could be sorted by popularity! 😅~~ [Edit: Wait…are they already sorted by popularity? That’s different than I remember! Now I won’t have to write that...