ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Joseph Jones <joeyi5216@gmail.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Cc: <ruby-core@ruby-lang.org>
Subject: [ruby-core:72334] [Ruby trunk - Feature #11100] Permit multiple captures with String[Regexp, ...]
Date: Thu, 17 Dec 2015 21:13:10 -0700	[thread overview]
Message-ID: <EB15638F-4E69-4228-9869-87E63E1BAEEC@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

Joseph Jones liked your message with Boxer. On December 10, 2015 at 16:35:21 MST, djberg96@gmail.com wrote:Issue #11100 has been updated by Daniel Berger.I support allowing multiple captures. I think the [1,2] syntax is the most intuitive.----------------------------------------Feature #11100: Permit multiple captures with String[Regexp, ...]https://bugs.ruby-lang.org/issues/11100#change-55454* Author: D.E. Akers* Status: Open* Priority: Normal* Assignee: ----------------------------------------I propose that if we are able to conveniently grab one capture with this method, we ought to be able to grab more than one. Still, there are some caveats worth considering:* It should return an array, but every other `#[]` variant returns a string or `nil`.* Should the argument be an array, or should the method be variadic? - Array argument looks a little "noisy"? `'123abc'[/(\d+)(\w+)/, [2, 1]]` - Variadic method requires intrusive modification of internal calls to `rb_str_subpat()`.* Complementary `#[]=` would be crpytic, overly complex, and likely go unused, but not adding it would break the symmetry.I realize this is essentially an outline of why not to implement this feature, but I figured I'd toss it out there for feedback. Thoughts?---Files--------------------------------string_slice_many_captures.patch (906 Bytes)-- https://bugs.ruby-lang.org/     

[-- Attachment #2: Type: text/html, Size: 1787 bytes --]

                 reply	other threads:[~2015-12-18  3:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=EB15638F-4E69-4228-9869-87E63E1BAEEC@gmail.com \
    --to=ruby-core@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).