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 6FB7C1F4CC for ; Sun, 5 Jan 2025 06:33:03 +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=0r9RElIh; 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=TpnIxCGr; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1736058750; bh=CFTk4RkUyv7ex5zlBj1o4kJcLVZ+5cSGLm5Az6YK9Fc=; 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=0r9RElIhFas39nUyqVPBgOtJTpVe6xa+UD+tNqKknQazGo1KkOQY+JYVcntEp+aTn DX6KZCqdQ0EQo1ms/TUiAOJJcUoMVJa9/CczEFuC1PzYr5NjbXueSopVsCQLil3Hcd /AAWX/+gh24Pl2JDzCChL0Kj5MzUFNndhQAm9oSo= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id D65D346516 for ; Sun, 5 Jan 2025 06:32:30 +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=TpnIxCGr; dkim-atps=neutral Received: from s.wrqvtzvf.outbound-mail.sendgrid.net (s.wrqvtzvf.outbound-mail.sendgrid.net [149.72.126.143]) by nue.mailmanlists.eu (Postfix) with ESMTPS id B3D5E463B3 for ; Sun, 5 Jan 2025 06:32:25 +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=0mO8+yxGutECO53SHEAizNWVlLsBOTeRwp9kvV3THu8=; b=TpnIxCGr8Yh89bNUwenkCqcdzRoZg7t3dFDz7aq0Aw7OjIe1ltbSkCk3IrYD/aRMs85S AmE8TSOrFLpx4FTeh1+pzFVkO42WD8eciqtynJ+cMwXc9euo2zHwssHR+vpLDuFxbSUbsK dQpX4UeTLZeSZhQyty+FuY1WT4cUCkcWWdDELeOJBFOJzgsppVX/hmp0XRJLWhuSHU8Ior ShYBLTmBZdWL6jgrt4YafZy7sjQIuPc9PwNXrKSjSImrw1jUyX9OTq6bZMptc4uhTkY8A0 GhzghjGnbzcL13+Y3whwJaWYIB8n7f6ki95X6eoo2c81xs4k5U1+cXFi1MKJQ81A== Received: by recvd-786d47b7ff-lqk94 with SMTP id recvd-786d47b7ff-lqk94-1-677A2778-A 2025-01-05 06:32:24.368242473 +0000 UTC m=+4439409.190127377 Received: from herokuapp.com (unknown) by geopod-ismtpd-36 (SG) with ESMTP id v6FzZfcwSzKg7XvnA3MSBQ for ; Sun, 05 Jan 2025 06:32:24.345 +0000 (UTC) Date: Sun, 05 Jan 2025 06:32:24 +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: rubyFeedback 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: 97158 X-SG-EID: =?us-ascii?Q?u001=2EruicwCtMXDP3tLBNCvXQCRaz73SB6rhUkPmHq3p2DFapywRWRkw1b65Eo?= =?us-ascii?Q?MrJD9a3+D07vVOYs8cdF9Tr82nM7sTgk1NsXSf8?= =?us-ascii?Q?YFQQEuNXzGx1V8gD9cnfDlvvCtOoZzt5+hSsM+P?= =?us-ascii?Q?LI3QQZVqWCOClJa6bfiVnY27GXi+lzoRsQrJmWz?= =?us-ascii?Q?BlJF81sUkWWImgvKbNGahE25MEseartBYerl8gl?= =?us-ascii?Q?dqRkDwuyUc5DU7fG3hUhIZDR6D+0LgYA6y7gQYt?= =?us-ascii?Q?+17Ue5glG7tR+ZQXjxZyQpsbJQ=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: KCHGQTDVJB2XGNITULXZJ3G3O3XHP7CA X-Message-ID-Hash: KCHGQTDVJB2XGNITULXZJ3G3O3XHP7CA 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:120482] [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: "rubyFeedback (robert heiler) via ruby-core" Cc: "rubyFeedback (robert heiler)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20770 has been updated by rubyFeedback (robert heiler). Personally I do not think I would need this feature (I share mame's opinion here), but what has not yet been pointed out is the language streem by matz (https://github.com/matz/streem). Now, streem is not ruby and matz has not pushed streem for a while, but I believe the basic gist (idea) for streem is one based around using pipes as a filter for data. This may not mean much in regards to ruby and the issue here, and I think one small issue is that in ruby we kind of do data-filtering via .method calls on objects, so |> may be somewhat orthogonal to this (or, at the least some suggestions of what |> should do exactly in ruby), but I think if we include streem's goals into consideration then matz may be open to suggestions for |> being useful in one way or another. I actually like |>, oddly enough, although as mame stated, I think there need to be some key reasons for using |> other than looking pretty. Magro wrote: > The pipe operator provides a predictable and explicit structure While I like |>, I think any proposal to cover |> needs to have a good use case. Perhaps there could be a set of suggestions in regards to |> and matz and the ruby core team may select one that seems the best in itself and the least orthogonal. (I think Elixir's use cases are a bit different, in ruby I feel I can just use .methods such as .select or .reject, so as said I think that use case, as mame pointed out, may be already covered, and for |> it may be better to have some key advantages over classical .method chaining.) ---------------------------------------- Feature #20770: A *new* pipe operator proposal https://bugs.ruby-lang.org/issues/20770#change-111266 * 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/