Project

General

Profile

Actions

Feature #9179

closed

MatchData#values_at should support named capture

Added by vzvu3k6k (vzvu3k6k _) almost 11 years ago. Updated over 8 years ago.

Status:
Closed
Target version:
-
[ruby-core:58701]

Description

=begin
Using (({MatchData#[]})), we can access a named capture by its name.

/(?...)/.match("foo")[:a] #=> "foo"
/(?
...)/.match("foo")["a"] #=> "foo"

But (({MatchData#values_at})) accepts only Integer and refuses Symbol or String.

/(?...)/.match("foo").values_at(:a)

I expected it returns ["foo"], but...

#=> in `values_at': no implicit conversion of Symbol into Integer (TypeError)

/(?...)/.match("foo").values_at("a")
#=> in `values_at': no implicit conversion of String into Integer (TypeError)

(These are tested in ruby 2.1.0dev (2013-11-28 trunk 43903) [i686-linux].)

I think (({MatchData#values_at})) should work along with (({MathData#[]})) as follows:

/(?...)/.match("foo").values_at(:a) #=> ["foo"]
/(?
...)/.match("foo").values_at("a") #=> ["foo"]

In the patch, (({match_entry})) is removed because it is no longer used. Comments and code are based on (({rb_hash_values_at})) in hash.c. It passes (({make test-all})) except (({TestGc#test_gc_reason})), which fails also on the original version.
=end


Files

matchdata-values_at-named_capture.diff (1.89 KB) matchdata-values_at-named_capture.diff vzvu3k6k (vzvu3k6k _), 11/29/2013 11:23 PM
Actions

Also available in: Atom PDF

Like0
Like0Like0