From: chris@... Date: 2019-06-14T05:42:03+00:00 Subject: [ruby-core:93129] [Ruby trunk Feature#15799] pipeline operator Issue #15799 has been updated by shioyama (Chris Salzberg). I think one big issue here is simply the choice of symbols for this thing. If it were any other symbols, I suspect a lot of people would not have reacted so emotionally. To most Rubyists who know it, `|>` has a distinctive meaning. It's that bit of functional programming that they want, that they wish Ruby had, that Elixir has had from day one. Whether you like it or not, the `.` alias here is entirely different from a "pipeline". Giving it the same name is bound to frustrate a lot of people (like myself) who have been hoping and waiting for the day when Ruby would support function composition in a more natural way. Barring a revert, how about considering a different pair of symbols for this thing? That would seem to be a reasonable compromise. ---------------------------------------- Feature #15799: pipeline operator https://bugs.ruby-lang.org/issues/15799#change-78558 * 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: