J. S. Choi

> I just noticed you added the `follow-on-proposal` label here. May I suggest considering named placeholder an alternative baseline instead? Whether to make declaring an identifier at each pipe step...

GitHub deleted my comment from yesterday, and I’m not sure why. I’m going to try to reproduce it… Like @mAAdhaTTah, I like your post a lot. I think it cuts...

> Adding these combinators to the core JavaScript API, while serving as a friendly nod to the FP in JS community, and perhaps even as inspiration to try FP for...

Thanks for the thanks! 🙂 But I don’t want to give false hope either. I do want to emphasize that, right now, I and the pipe champion team are set...

Mm, #227 is about a different topic. This topic is merely about documenting tc39/proposal-hack-pipes#18, which is just the fact that TypeScript currently *already* cannot automatically infer the types of curried...

> Thanks for trying to emphasize with the people on the F# side even when you are on the hack side. As always which such polarizing issues, people almost never...

> @js-choi > First of all, thank you for opening the issue of this aspect and I also appreciate your hard work (must be, I guess) for [Brief history of...

> My opinion on this is based on an idea that I've seen floating around in other thread about the "tax" that comes with each style. People will often take...

@mohaalak: This is somewhat covered in #221 and https://github.com/tc39/proposal-pipeline-operator/issues/202#issuecomment-918595019. Like #221 talks about, [F# pipes and smart-mix pipes have run into a lot of deep concerns from TC39 representatives outside...

I appreciate this issue because it gets to the heart of a lot of the disputation. Kudos here to @treybrisbane for doing so. We should have addressed this in the...