| 23:56 | <jschoi> | Did "pipe should belong in the future jssugar layer" block advancement to stage 3? JSSugar did not block the pipe operator from Stage 3 because the pipe operator has never been formally proposed for Stage 3. Every plenary timeslot since it advanced to Stage 2 in 2021 has been devoted to bikeshedding about its syntax or its overlap with the other dataflow proposals https://github.com/tc39/proposal-pipeline-operator/blob/main/HISTORY.md. JSSugar was formally proposed in October 2024 https://github.com/tc39/notes/blob/main/meetings/2024-10/october-08.md. My understanding is that nothing concrete has happened for JSSugar since then, except for vague rumblings from sympathetic engine implementers. Someone correct me if I’m wrong. |