Mickey Rose

@nobodyinperson docs won't fix this issue. It has nothing to do with oniguruma being a git submodule. The issue is not missing submodule sources. It is about the release source...

> But more importantly is the relation of `|>` to `=>`; F#-style _has_ to have unparenthesized arrow-funcs in pipe bodies to be competitive with any other style (otherwise you're paying...

> I would love to know if there is a more compelling way of illustrating that F# pipes would require the developer to distinguish between “expression that resolves to an...

It took me a while to realize that I suggested the exact same thing in another topic a few days after @shuckster, apologies for not giving proper credit, I must've...

@js-choi I just noticed you added the `follow-on-proposal` label here. May I suggest considering named placeholder an alternative baseline instead? If we started with grammar such as: `Expr |> BindingIdentifier...

> By the time we’re naming variables, we might as well be just using variable assignment, right? No. Because apples-to-apples equivalent would use const which you can't re-assign. Also variables...

> The existing piping syntaxes in JS (method chaining, userland pipe()) don't name the topic variable being passed between each stage, and that still makes for perfectly reasonable and readable...

@mAAdhaTTah > ... based on the fact that tacit style programming, which F# pipe encourages, requires currying/unary functions/HOF ... Even though most of you have dismissed Elixir pipe as unfit...

> This is the case where they're not identical: > > ```js > // F# > x |> add(1) > // Hack > x |> add(1, ^) > ``` >...

> Here it is with Hack pipes: > > ```js > const repeat = (duration) => (notes$) => > periodic(duration) > |> map(() => notes$ |> until(at(duration))(^)))(^); > ``` Yes,...