tc39/proposal-pipeline-operator issues and pull requests

#307 - Playground for bikeshedding the topic token?

Issue - State: open - Opened by bogdanbiv about 2 months ago

#306 - What is the current state of this proposal?

Issue - State: closed - Opened by VitorLuizC about 2 months ago - 2 comments
Labels: question

#305 - Pattern Matching in Pipes

Issue - State: closed - Opened by triyanox about 2 months ago - 7 comments

#304 - Function composition models pipelines

Issue - State: closed - Opened by mlanza 4 months ago - 2 comments

#303 - Implementing pipeline operator as a syntax transformer

Issue - State: open - Opened by dmchurch 5 months ago - 7 comments

#302 - A simpler, proposed alternative to existing proposals

Issue - State: closed - Opened by matthew-dean 8 months ago - 5 comments

#301 - Fix Clojure's shorthand param syntax in README

Pull Request - State: closed - Opened by vendethiel 10 months ago - 4 comments

#300 - Piping streams?

Issue - State: closed - Opened by ReinsBrain 12 months ago - 1 comment

#299 - Error Handling

Issue - State: closed - Opened by lauhon about 1 year ago - 3 comments

#298 - Kotlin-style pipelines

Issue - State: closed - Opened by alamothe about 1 year ago - 3 comments

#297 - I think it would be prudent to walk away from this proposal entirely

Issue - State: closed - Opened by benlesh over 1 year ago - 12 comments

#296 - New motivation

Issue - State: open - Opened by lilnasy over 1 year ago - 2 comments

#295 - Make topic token optional in hack proposal in some cases

Issue - State: closed - Opened by dword-design over 1 year ago - 6 comments

#294 - Combine Hack and F# Pipes

Issue - State: closed - Opened by ethanlal04 over 1 year ago - 4 comments

#293 - Need to make a convincing argument why this can't be a library function

Issue - State: closed - Opened by pyrocto over 1 year ago - 2 comments

#292 - Fix typo in README

Pull Request - State: closed - Opened by berenar over 1 year ago

#291 - Fix the spelling error of the example in README

Pull Request - State: closed - Opened by k644606347 over 1 year ago

#290 - Grammar rules in proposed spec text seem incomplete

Issue - State: open - Opened by sethbrenith over 1 year ago - 2 comments

#289 - Use @ instead of % as % is already an operator

Issue - State: closed - Opened by Mike96Angelo over 1 year ago - 4 comments

#288 - Simpler Syntax

Issue - State: closed - Opened by no-gravity over 1 year ago - 11 comments

#285 - Is there a place where we can just say "please no"?

Issue - State: closed - Opened by taoeffect over 1 year ago - 8 comments

#284 - Proposal: create a new function instead

Issue - State: closed - Opened by JamesJansson over 1 year ago - 8 comments

#283 - Raku-style pipelining with less verbose lambda syntax

Issue - State: closed - Opened by C-Ezra-M almost 2 years ago - 1 comment

#282 - Solution - Two operators?

Issue - State: closed - Opened by bryanrideshark almost 2 years ago - 1 comment

#281 - What if? Use `->` instead `|>`

Issue - State: closed - Opened by mikoloism about 2 years ago - 3 comments
Labels: question, wontfix

#280 - Fix link to F# pipes proposal

Pull Request - State: closed - Opened by kidonng about 2 years ago - 1 comment

#279 - Wrong "F# pipes" link?

Issue - State: closed - Opened by kidonng about 2 years ago - 3 comments

#278 - Proposition: supporting both options by making the Hack syntax a sugar syntax for unary functions

Issue - State: closed - Opened by sharshuv-quotient about 2 years ago - 5 comments
Labels: question

#277 - Implementation of pipe with existing ECMAScript features

Issue - State: closed - Opened by sharshuv-quotient about 2 years ago - 2 comments
Labels: duplicate

#276 - Combining `|>` with `=>`

Issue - State: open - Opened by getify about 2 years ago - 2 comments
Labels: follow-on proposal

#275 - Could `|>` be amended with a `...` spread?

Issue - State: closed - Opened by getify about 2 years ago - 38 comments
Labels: question

#274 - Placeholder name, eg %name

Issue - State: open - Opened by pie6k about 2 years ago - 9 comments
Labels: follow-on proposal

#273 - Compare pipeline syntax operators with API function calls

Issue - State: open - Opened by sffc about 2 years ago - 1 comment
Labels: question, documentation

#272 - Related topic: pipe syntax for if-catch section

Issue - State: closed - Opened by natserract over 2 years ago - 6 comments

#271 - Pipeline vs Semicolon

Issue - State: closed - Opened by xp44mm over 2 years ago - 7 comments

#270 - Can pipleline operator simplify try {} catch {} boilerplate codes?

Issue - State: closed - Opened by lygstate over 2 years ago - 2 comments

#269 - Is the pipeline proposal blocked?

Issue - State: closed - Opened by theScottyJam over 2 years ago - 4 comments
Labels: question

#268 - explainer/spec: Switch topic from % to @

Pull Request - State: closed - Opened by js-choi over 2 years ago - 2 comments

#267 - Advice : use `pipe` be a keyword

Issue - State: closed - Opened by WingDust over 2 years ago - 1 comment
Labels: wontfix

#266 - Special case unary hack operator part 2

Issue - State: closed - Opened by cowboyd over 2 years ago - 2 comments
Labels: question

#265 - The '%' symbol possibly conflicting with the modulo operator?

Issue - State: closed - Opened by shovon over 2 years ago - 1 comment

#264 - use detailed link

Pull Request - State: closed - Opened by linbudu599 over 2 years ago

#263 - spec/explainer: Clarify “precedence” with conditional expressions

Pull Request - State: closed - Opened by js-choi over 2 years ago
Labels: bug, documentation

#262 - Placeholder scope/visibility

Issue - State: open - Opened by dy over 2 years ago - 16 comments
Labels: question

#261 - Usefulness of placeholder outside of pipes

Issue - State: closed - Opened by dy over 2 years ago - 2 comments

#260 - Special case unary hack operator?

Issue - State: closed - Opened by cowboyd over 2 years ago - 6 comments
Labels: follow-on proposal

#259 - Adding an inverted pipeline to help with callbacks

Issue - State: closed - Opened by theScottyJam over 2 years ago - 11 comments
Labels: follow-on proposal

#258 - fix: "b(%)" -> "g(%)"

Pull Request - State: closed - Opened by sweetliquid almost 3 years ago
Labels: documentation

#257 - A blend of Hack and F# pipes via a unary function shorthand

Issue - State: closed - Opened by zzzzBov almost 3 years ago - 13 comments
Labels: enhancement

#256 - history: Update with 2021-10 plenary results

Pull Request - State: closed - Opened by js-choi almost 3 years ago
Labels: documentation

#255 - spec: Change Contains to ContainsOuterTopic

Pull Request - State: closed - Opened by js-choi almost 3 years ago
Labels: bug

#254 - Add temp var to real-world examples

Pull Request - State: closed - Opened by vjpr almost 3 years ago - 7 comments
Labels: documentation

#253 - Real-world examples should show refactored code with temp vars

Issue - State: closed - Opened by vjpr almost 3 years ago - 3 comments
Labels: wontfix, documentation

#252 - Arrow function used improperly when using the F# pipe to create an object

Issue - State: closed - Opened by tripplyons almost 3 years ago - 1 comment

#251 - How's gonna be treated nested operators?

Issue - State: closed - Opened by vadzim almost 3 years ago - 5 comments
Labels: question

#250 - Revert change from % to ^

Pull Request - State: closed - Opened by js-choi almost 3 years ago

#247 - Consider rescript style pipe

Issue - State: closed - Opened by theqp almost 3 years ago - 4 comments

#245 - Instead of an operator just a pipe function?

Issue - State: closed - Opened by theqp almost 3 years ago - 2 comments
Labels: duplicate

#244 - Add @littledan as former champion

Pull Request - State: closed - Opened by js-choi almost 3 years ago
Labels: documentation

#242 - F# Pipe Operator as Syntactic Sugar

Issue - State: closed - Opened by lilnasy almost 3 years ago - 5 comments
Labels: question

#241 - explainer: Create § Relationships, other proposals

Pull Request - State: closed - Opened by js-choi almost 3 years ago - 2 comments
Labels: documentation

#240 - Patch to README.md

Pull Request - State: closed - Opened by FrameMuse almost 3 years ago - 2 comments
Labels: documentation

#239 - Readme indents change

Issue - State: closed - Opened by FrameMuse almost 3 years ago - 1 comment
Labels: question, documentation

#238 - README: Method Chaining probably shouldn't be mentioned?

Issue - State: open - Opened by benlesh almost 3 years ago - 22 comments
Labels: question, documentation

#237 - Viability of using |: as the operator for Hack-style

Issue - State: closed - Opened by shuckster almost 3 years ago - 26 comments
Labels: question, bikeshed

#236 - explainer: Pipes with method chaining in React example

Pull Request - State: closed - Opened by js-choi almost 3 years ago - 2 comments

#235 - unconvincing example in readme part Hack pipes might be simpler to use

Issue - State: open - Opened by lightmare almost 3 years ago - 7 comments
Labels: question, documentation

#233 - In defense of unary functions

Issue - State: open - Opened by Avaq almost 3 years ago - 19 comments
Labels: question, documentation

#232 - Official changes thread

Issue - State: open - Opened by js-choi almost 3 years ago - 6 comments
Labels: announcement

#231 - Floodgate Bot

Issue - State: open - Opened by js-choi almost 3 years ago
Labels: announcement

#226 - Minor spec bugs

Issue - State: closed - Opened by Fayti1703 almost 3 years ago - 6 comments
Labels: bug, documentation

#225 - Effect of Hack proposal on code readability

Issue - State: closed - Opened by arendjr about 3 years ago - 299 comments
Labels: question, documentation

#222 - Role of popularity in the explainer

Issue - State: open - Opened by js-choi about 3 years ago - 6 comments
Labels: documentation

#221 - Prior difficulty persuading TC39 about F# pipes and PFA

Issue - State: open - Opened by js-choi about 3 years ago - 34 comments
Labels: documentation

#220 - Relationship between PFA syntax and Hack pipes

Issue - State: closed - Opened by js-choi about 3 years ago
Labels: documentation

#217 - Impact of Hack pipes on the JS functional-programming ecosystem

Issue - State: open - Opened by js-choi about 3 years ago - 72 comments
Labels: documentation

#216 - Role of usability studies in the explainer

Issue - State: open - Opened by js-choi about 3 years ago
Labels: documentation

#215 - Frustrations of people looking forward to tacit syntax

Issue - State: open - Opened by js-choi about 3 years ago - 42 comments
Labels: question, documentation

#214 - Community-health and history documents

Pull Request - State: closed - Opened by js-choi about 3 years ago - 1 comment
Labels: documentation

#211 - Add arguments for why pipelines are better than mutable temporary variables

Pull Request - State: closed - Opened by loreanvictor about 3 years ago - 8 comments

#206 - Tacit programming / point-free style and pipes

Issue - State: open - Opened by treybrisbane about 3 years ago - 58 comments
Labels: question, documentation

#203 - Named placeholders

Issue - State: open - Opened by shuckster about 3 years ago - 38 comments
Labels: follow-on proposal

#202 - Separate (complementary) F# pipeline proposal?

Issue - State: open - Opened by mmkal about 3 years ago - 51 comments
Labels: follow-on proposal

#198 - Optional Hackpipes proposal

Issue - State: open - Opened by webduvet about 3 years ago - 17 comments
Labels: enhancement, follow-on proposal

#193 - Update README wiki links

Pull Request - State: closed - Opened by advaith1 about 3 years ago
Labels: documentation

#188 - Interaction with the wavy dot proposal?

Issue - State: closed - Opened by dead-claudia over 3 years ago - 5 comments

#187 - Skip the operator?

Issue - State: closed - Opened by staeke over 3 years ago - 4 comments

#185 - Pipelining with `then` and `to`, and `it`.

Issue - State: closed - Opened by ghost over 3 years ago - 3 comments

#183 - Update README.md

Pull Request - State: closed - Opened by tomByrer over 3 years ago - 5 comments

GitHub / tc39/proposal-pipeline-operator issues and pull requests