From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 5994D1F531 for ; Mon, 10 Aug 2020 16:47:31 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 0C98B12093B; Tue, 11 Aug 2020 01:46:57 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 3887112093A for ; Tue, 11 Aug 2020 01:46:54 +0900 (JST) Received: by filterdrecv-p3las1-559bd7b968-682tx with SMTP id filterdrecv-p3las1-559bd7b968-682tx-19-5F317A15-2A 2020-08-10 16:47:17.277519112 +0000 UTC m=+1031476.255320921 Received: from herokuapp.com (unknown) by geopod-ismtpd-1-2 (SG) with ESMTP id Sm79U8_cQe2GuJ1vzrTRpg for ; Mon, 10 Aug 2020 16:47:17.120 +0000 (UTC) Date: Mon, 10 Aug 2020 16:47:17 +0000 (UTC) From: finch.parker@gmail.com Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 75370 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Feature X-Redmine-Issue-Id: 17016 X-Redmine-Issue-Author: parker X-Redmine-Sender: parker 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-SG-EID: =?us-ascii?Q?pwrarsM0T2iL4aPgLngF2+VbEmD0Mx5cfa5PXbdWp+Z6qCdST02cHi0mTUvQ6E?= =?us-ascii?Q?skSknIZBk3xSsLZMDy9cb1IdE5NZ834ykAnBBOq?= =?us-ascii?Q?ZhvX4+eeOSqY8BHIdaEYFleH7r5DLPxWEALrXPI?= =?us-ascii?Q?3U08NNhewQm7=2FT6ZXw5=2FG+oaDGIUY=2FMy+fqE7qe?= =?us-ascii?Q?RLaiLH034tFt+PH3CTEWGqXpbvjnI2Ro5qcl5wI?= =?us-ascii?Q?EZB7=2Fk7C7+UkSmX0Y=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 99545 Subject: [ruby-core:99545] [Ruby master Feature#17016] Enumerable#scan_left X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #17016 has been updated by parker (Parker Finch). nobu (Nobuyoshi Nakada) wrote in #note-30: > I found a word [traject], means to transport, transmit, or transpose. > It may (or may not) imply [trajectory]... > > [traject]: https://www.dictionary.com/browse/traject > [trajectory]: https://www.dictionary.com/browse/trajectory That's an interesting word that I don't know. It looks like it's archaic, so I don't think that it has much meaning anymore. That's kind of nice, since there's not a conflicting definition that people will have in their heads. However, it also doesn't have a meaning that describes what the method does. It does have a nice symmetry with `inject` though! Curious if others have thoughts? ---------------------------------------- Feature #17016: Enumerable#scan_left https://bugs.ruby-lang.org/issues/17016#change-87004 * Author: parker (Parker Finch) * Status: Open * Priority: Normal ---------------------------------------- ## Proposal Add a `#scan_left` method to `Enumerable`. (The name "scan_left" is based on Scala's scanLeft and Haskell's scanl. It seems like "scan_left" would be a ruby-ish name for this concept, but I'm curious if there are other thoughts on naming here!) ## Background `#scan_left` is similar to `#inject`, but it accumulates the partial results that are computed. As a comparison: ``` [1, 2, 3].inject(0, &:+) => 6 [1, 2, 3].scan_left(0, &:+) => [0, 1, 3, 6] ``` Notably, the `scan_left` operation can be done lazily since it doesn't require processing the entire collection before computing a value. I recently described `#scan_left`, and its relationship to `#inject`, more thoroughly in [this blog post](https://medium.com/building-panorama-education/scan-left-a-lazy-incremental-alternative-to-inject-f6e946f74c00). ## Reasoning We heavily rely on the scan operation. We use an [event-sourcing](https://martinfowler.com/eaaDev/EventSourcing.html) pattern, which means that we are scanning over individual "events" and building up the corresponding state. We rely on the history of states and need to do this lazily (we stream events because they cannot fit in memory). Thus the scan operation is much more applicable than the inject operation. We suspect that there are many applications that could leverage the scan operation. [This question](https://stackoverflow.com/questions/1475808/cumulative-array-sum-in-ruby) would be more easily answered by `#scan_left`. It is a natural fit for any application that needs to store the incrementally-computed values of an `#inject`, and a requirement for an application that needs to use `#inject` while maintaining laziness. ## Implementation There is a Ruby implementation of this functionality [here](https://github.com/panorama-ed/scan_left/) and an implementation in C [here](https://github.com/ruby/ruby/pull/3078). ## Counterarguments Introducing a new public method is committing to maintenance going forward and expands the size of the Ruby codebase -- it should not be done lightly. I think that providing the functionality here is worth the tradeoff, but I understand any hesitation to add yet more to Ruby! ---Files-------------------------------- scan_left_example.rb (2.93 KB) -- https://bugs.ruby-lang.org/