| 00:17 | <jschoi> | If I’m understanding correctly…it sounds like you’re concerned that we’re focusing overmuch on the pipe operator and thinking of the other proposals in terms of the pipe operator. TC39 has not only talking about the pipe operator. We focused on many other proposals in the dataflow meetings on Wednesday and Thursday meetings. |
| 00:17 | <ljharb> | pipeline's already been saddled with that tho, since when it was first presented for stage 1 many years ago, people wanted that to kill the bind operator |
| 00:20 | <jschoi> | Well, I guess it’s true that the pipe operator might affect all the other proposals, insofar that people don’t like excessive overlap. And some people want to prioritize the pipe operator. But we’re still talking about the other proposals on their own merits. In the specific case of the overlap between pipe operator and bind-this/call-this, we all resolved on Thursday that the overlap between the two is not excessively bad, and nobody would block either—at least solely based on that overlap. (Though I know at least one representative who wasn’t present at the time who might be skeptical of this conclusion…) The same goes for the pipe operator versus Function.pipe. In the case of the other proposals, like Extensions and PFA syntax, we’re taking it on a case-by-case basis. |
| 00:22 | <pokute> | Thanks, It resolves almost all my worrying. |