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=0.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS, SPF_PASS autolearn=no 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) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DD8C91F5CB for ; Mon, 30 Sep 2024 04:28:06 +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=AqBYyY7b; 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=pdTFTEVE; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1727670454; bh=5A/I2ojZEvrz30O7HEM1HOnYALVsqm5xOV/OSyA7oIM=; 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=AqBYyY7br1Q5cMVPI8Gz2k2/zOjptuNTn2LM4Uw6e6QC4qupjLsZXzE7YwoSujspd g9ZI5IZjixsIkLU+hJDrws4KODnJe4JBvZZYG8lDl0QaP22fH32QGwMXFHaBqWk3Mh CsBxcGQdq7gUzo6h3owvvkxbMZogP1eRH4ZsVmAU= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 6BB9643F88 for ; Mon, 30 Sep 2024 04:27:34 +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=pdTFTEVE; dkim-atps=neutral Received: from s.wrqvtbkv.outbound-mail.sendgrid.net (s.wrqvtbkv.outbound-mail.sendgrid.net [149.72.123.24]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 08F0C43E9C for ; Mon, 30 Sep 2024 04:27: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=cQAaUr1bNQ2hEmiM0G9cFZ1epIjaOzbZiovSNPiFY1E=; b=pdTFTEVEaOeWcLeEHcg9W8b/dGn/UwPJfIZRjfDA7cW9uOFESlqYUL26ziOjN84wbYNT SrReVKiaeEdoON9kGSdNbytwVD4RkUPto3JpL/Pon5CMe1vLMhuVfABKwg75E/fNIQBJ4I aiNv2M9YUaseWCvGZ+vQHRyfqmiCrPPWOPnKdVGyMh3a7ir2/tWeMaJmlklUI5T5z9yxm/ OiAvpduyQ7Rd8bDX+T73jLh5/qg+NCUpTOCdJ24VR0aygfhUCkGn7aef6j0/5wMyxgHKL1 LtlbrT2QhWUjq2KciQrQHYE7YnmxvB9JBflDJSlrdbwZX01m1FT05IYvEHGSk0eQ== Received: by recvd-d66cff667-ddh9z with SMTP id recvd-d66cff667-ddh9z-1-66FA28AA-D 2024-09-30 04:27:22.60996142 +0000 UTC m=+1506673.830341754 Received: from herokuapp.com (unknown) by geopod-ismtpd-25 (SG) with ESMTP id oVCdTYPCSCawXP4x7I68Vw for ; Mon, 30 Sep 2024 04:27:22.535 +0000 (UTC) Date: Mon, 30 Sep 2024 04:27:22 +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: shuber 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: 95977 X-SG-EID: =?us-ascii?Q?u001=2Eoe1X9F9mzi2xray9UKpOHwR+YHaZ5aEaVhI0+h2TEtcDyPMjdglUiDUTt?= =?us-ascii?Q?E3PZ2ZHOeaNFD492FvV7jbUkj=2FTYD4=2F8GzCMIGs?= =?us-ascii?Q?NTDg7ur5DFebffiHSLqauF1riu1bpcAUElmq9fP?= =?us-ascii?Q?xD2mr3+aYBPii3Y425cStHa8qHRmjPklPVzox1l?= =?us-ascii?Q?HxgOXdEM=2Ffe63q892LI83j9CfJ6wFxrWsHWv0yo?= =?us-ascii?Q?LkALaEG0EGPRlPAwL83FVzhavpD5g8cAOK7VdKA?= =?us-ascii?Q?qkvM?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: DIMFFSHO5LGHWKEQK5Z5QD5IVLQTIOIU X-Message-ID-Hash: DIMFFSHO5LGHWKEQK5Z5QD5IVLQTIOIU 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:119341] [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: "shuber (Sean Huber) via ruby-core" Cc: "shuber (Sean Huber)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20770 has been updated by shuber (Sean Huber). I would still love to see this type of pipeline functionality implemented with plain expressions instead of new operators. I have this (old) working [proof of concept](https://github.com/lendinghome/pipe_operator#-pipe_operator) gem from years ago (basic syntax described below) but it was primarily focused on constant interception. I imagine it can be quite a bit more complex adding support for calling Proc objects and other edge cases. ```ruby "https://api.github.com/repos/ruby/ruby".pipe do URI.parse Net::HTTP.get JSON.parse.fetch("stargazers_count") yield_self { |n| "Ruby has #{n} stars" } Kernel.puts end #=> Ruby has 22120 stars -9.pipe { abs; Math.sqrt; to_i } #=> 3 [9, 64].map(&Math.pipe.sqrt.to_i.to_s) #=> ["3", "8"] ``` Most of the logic in that proof of concept was related to intercepting method calls to ALL constants which wouldn't be necessary if it was a core part of the language. The actual "pipeline" functionality (`PipeOperator::Pipe` and `PipeOperator::Closure`) is pretty simple - basically just keeping an array of constant+method+args calls and `reduce`ing the result when the pipeline ends. The proof of concept is basically `prepend`ing a version of every method in every constant with something like the example below in order to support this "pipeline expressions" syntax: ```ruby define_method(method) do |*args, &block| if Pipe.open Pipe.new(self).__send__(method, *args, &block) else super(*args, &block) end end ``` https://github.com/lendinghome/pipe_operator#-pipe_operator ---------------------------------------- Feature #20770: A *new* pipe operator proposal https://bugs.ruby-lang.org/issues/20770#change-109952 * 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/