From: eregontp@... Date: 2019-06-13T10:00:52+00:00 Subject: [ruby-core:93103] [Ruby trunk Feature#15799] pipeline operator Issue #15799 has been updated by Eregon (Benoit Daloze). Why was this accepted? I cannot see anyone really supporting this idea in this issue's comments. As everyone said, it hurts readability, looks like Haskell, and there seems to be really no need for a different syntax for methods calls. The example in the commit seems very unconvincing to me: ```ruby # today x = (12 ** 2).to_s(11) # the new syntax x = 12 |> pow(2) |> to_s(11) ``` It's even much longer. ---------------------------------------- Feature #15799: pipeline operator https://bugs.ruby-lang.org/issues/15799#change-78527 * Author: nobu (Nobuyoshi Nakada) * Status: Closed * Priority: Normal * Assignee: * Target version: ---------------------------------------- Implemented the pipeline operator `|>`, a topic of "ruby committers vs the world" in RubyKaigi 2019. Also a casual idea of rightward assignment. ```ruby 1.. |> take 10 |> map {|e| e*2} |> (x) p x #=> [2, 4, 6, 8, 10, 12, 14, 16, 18, 20] ``` https://github.com/nobu/ruby/tree/feature/pipeline -- https://bugs.ruby-lang.org/ Unsubscribe: