ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "joshuay03 (Joshua Young) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "joshuay03 (Joshua Young)" <noreply@ruby-lang.org>
Subject: [ruby-core:114309] [Ruby master Feature#19787] Add Enumerable#uniq_map, Enumerable::Lazy#uniq_map, Array#uniq_map and Array#uniq_map!
Date: Sat, 29 Jul 2023 14:13:01 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-19787.20230729141300.52912@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19787.20230729141300.52912@ruby-lang.org

Issue #19787 has been reported by joshuay03 (Joshua Young).

----------------------------------------
Feature #19787: Add Enumerable#uniq_map, Enumerable::Lazy#uniq_map, Array#uniq_map and Array#uniq_map!
https://bugs.ruby-lang.org/issues/19787

* Author: joshuay03 (Joshua Young)
* Status: Open
* Priority: Normal
----------------------------------------
I would like to propose a collection of new methods, `Enumerable#uniq_map`, `Enumerable::Lazy#uniq_map`, `Array#uniq_map` and `Array#uniq_map!`.

TL;DR: It's a drop in replacement for `.map { ... }.uniq`, with better performance.

I've quite often had to map over an array and get its unique elements. It occurred to me when doing so recently that Ruby doesn't have a short form method for doing that, similar to how `flat_map { ... }` replaces `.map { ... }.flatten` and `filter_map { ... }` replaces `.map { ... }.compact` (with minor differences). I think these new methods could be beneficial both in terms of better performance and writing more succinct code.

I have already got a draft PR up with some initial benchmarks in the description: https://github.com/ruby/ruby/pull/8140.



-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/

       reply	other threads:[~2023-07-29 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 14:13 joshuay03 (Joshua Young) via ruby-core [this message]
2023-07-31  8:40 ` [ruby-core:114313] [Ruby master Feature#19787] Add Enumerable#uniq_map, Enumerable::Lazy#uniq_map, Array#uniq_map and Array#uniq_map! mame (Yusuke Endoh) via ruby-core
2023-07-31 10:13 ` [ruby-core:114314] " joshuay03 (Joshua Young) via ruby-core
2023-07-31 14:22 ` [ruby-core:114320] " austin (Austin Ziegler) via ruby-core
2023-07-31 14:50 ` [ruby-core:114321] " rubyFeedback (robert heiler) via ruby-core
2024-03-16  3:30 ` [ruby-core:117198] " joshuay03 (Joshua Young) via ruby-core
2024-03-16  3:40 ` [ruby-core:117199] " joshuay03 (Joshua Young) via ruby-core

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-19787.20230729141300.52912@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).