From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [94.130.110.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id A49471F4C4 for ; Sat, 9 Nov 2024 03:22:07 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=UY+8S39k; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=KjTrm1a6; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1731122495; bh=tWE7ZSI7foZQWpglXlz9G/cAoZKlk+HiZJrhs9C0k14=; h=Date:References:To:Reply-To:Subject:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From:Cc:From; b=UY+8S39kp9Vd1xnqg6YXNaVqQNLTYS+sxQvrPpIxa5pzMjE2y1gatahzE68UDy4AX R41rlPoSJ2CP07BK2BVld5go/Cj8H7iD2fLMz9R/DHOblCJR/zcoKM+cXhjITXbXPT a7DkvcC1bxrfPDUeAnVg2rE+vXXil31XNl7zEQt4= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 20D6844B6B for ; Sat, 9 Nov 2024 03:21:35 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=pass (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=KjTrm1a6; dkim-atps=neutral Received: from s.wrqvwxzv.outbound-mail.sendgrid.net (s.wrqvwxzv.outbound-mail.sendgrid.net [149.72.154.232]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 46D4C4463C for ; Sat, 9 Nov 2024 03:21:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=vFg5uEwU5nfiPha6fONAHc+AYBVYHgFG61R2FNLjL84=; b=KjTrm1a6Z0fF7Yh6cVwSaOn0jdPnCiC1L8kKH6+5kFYh4xxAos+J0IJNNVzVXT7MhYnG ejh/kiFqAcqr8Da0pe0O7nmp+7oHtVFLHEgTpf2hFfi46UwrLFNFF8A1tEHZ/9PetF3Q2K 3NFg8+0qUURaERbX7Q5GAR1MzR7XM6gfIlU/dQ7IuldJzaSPviuudnsiojb2GvYGZwug4n KplKyq3oiMkV7zoX0Gf2U2xLdJX0JIq+29EwoZu9miTft2eIE6/C++uHXiEp/HLLpys1JE Yiw2u0SLUUd8fXga7K3VFfUfF4gmwjnTObcjVxif+51IA70zugLeCtXJQBrWNbCQ== Received: by recvd-d66cff667-t9ht8 with SMTP id recvd-d66cff667-t9ht8-1-672ED531-B 2024-11-09 03:21:21.579369119 +0000 UTC m=+4958566.810007148 Received: from herokuapp.com (unknown) by geopod-ismtpd-39 (SG) with ESMTP id k4w8i1b4SwCBwh8peBjTMw for ; Sat, 09 Nov 2024 03:21:21.425 +0000 (UTC) Date: Sat, 09 Nov 2024 03:21:21 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Feature X-Redmine-Issue-Id: 20770 X-Redmine-Issue-Author: AlexandreMagro X-Redmine-Issue-Priority: Normal X-Redmine-Sender: baweaver X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 96527 X-SG-EID: =?us-ascii?Q?u001=2EV4PCrK+QfeHdk8C7QtR4rQXQ6DtfzAWKqcmJeOSBRz4KDX6dxLLJGhMYC?= =?us-ascii?Q?coZOSF7GSmxzFEZKNIR37Tx0Tsoiz=2F3PTnla6Mm?= =?us-ascii?Q?eUkNap2NPhRevJJHKz5fuXG912v0px=2FwUDCOSkv?= =?us-ascii?Q?YpJGBHLBUfOpMXn5=2FL3r9uvEYUcUAxlTihlrMpv?= =?us-ascii?Q?9L4wWka9CDnIf89KL8=2Fcu=2FrhWJNX5FpLgpnXHlg?= =?us-ascii?Q?I1N8Cq44K4pfldp4XbmiDS+F2MI1wkI7BA0lSnL?= =?us-ascii?Q?E31qqaGc7zhg2XBgBLPg6Nvveg=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: IMQCTY6POFXLR2Z2WSXYQZOMFDAJL4PP X-Message-ID-Hash: IMQCTY6POFXLR2Z2WSXYQZOMFDAJL4PP X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:119859] [Ruby master Feature#20770] A *new* pipe operator proposal List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "baweaver (Brandon Weaver) via ruby-core" Cc: "baweaver (Brandon Weaver)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20770 has been updated by baweaver (Brandon Weaver). I'd written on the previous iteration of the pipeline operator a while ago here: https://dev.to/baweaver/ruby-2-7-the-pipeline-operator-1b2d The ending example of what I thought, at the time, was an ideal state of it was: ```ruby double = -> v { v * v } increment = -> v { v + 1 } 5 |> double |> increment |> to_s(2) |> reverse |> to_i ``` ...which mixed both methods and procs to effectively pretend that Ruby was a LISP-1 derivative language, if only for the sake of pipelines. I believe that given the LISP-2 nature of the language this would be confusing, and add complexity for not a lot of practical gain compared to the combination of `then` and `it`. Frequently what folks are looking for is a nicer way to say this: ```ruby def some_method(v) = v + 1 5.then(&method(:some_method)) ``` ...and there have been a few proposals in that spirit before like `.:`: ```ruby HTTP.get(some_url).then(&JSON.:parse) ``` ...which I still think is an interesting potential syntax, and when applied to some of the pipeline proposals may become something like this: ```ruby HTTP.get(some_url) |> JSON.:parse |> filter { |k, v| v.is_a?(Integer) } ``` But again, comparatively speaking there's not a lot of overhead to `then` and `it` in those cases: ```ruby HTTP.get(some_url) .then { JSON.parse(it) } .filter { |k, v| v.is_a?(Integer) } ``` ...except to add more syntax that may be unclear for newer Ruby programmers that will be very hard to find documentation for. Even if I would very much like a shorter way to say `Object.method(:something)` I debate if it would be wise. ---------------------------------------- Feature #20770: A *new* pipe operator proposal https://bugs.ruby-lang.org/issues/20770#change-110549 * Author: AlexandreMagro (Alexandre Magro) * Status: Open ---------------------------------------- Hello, This is my first contribution here. I have seen previous discussions around introducing a pipe operator, but it seems the community didn't reach a consensus. I would like to revisit this idea with a simpler approach, more of a syntactic sugar that aligns with how other languages implement the pipe operator, but without making significant changes to Ruby's syntax. Currently, we often write code like this: ```ruby value = half(square(add(value, 3))) ``` We can achieve the same result using the `then` method: ```ruby value = value.then { add(_1, 3) }.then { square(_1) }.then { half(_1) } ``` While `then` helps with readability, we can simplify it further using the proposed pipe operator: ```ruby value = add(value, 3) |> square(_1) |> half(_1) ``` Moreover, with the upcoming `it` feature in Ruby 3.4 (#18980), the code could look even cleaner: ```ruby value = add(value, 3) |> square(it) |> half(it) ``` This proposal uses the anonymous block argument `(_1)`, and with `it`, it simplifies the code without introducing complex syntax changes. It would allow us to achieve the same results as in other languages that support pipe operators, but in a way that feels natural to Ruby, using existing constructs like `then` underneath. I believe this operator would enhance code readability and maintainability, especially in cases where multiple operations are chained together. Thank you for considering this proposal! -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/