Issue #19591 has been updated by mame (Yusuke Endoh). Discussed at the dev meeting. @matz accepted this, but he also said that the keyword should be `symbolize_names`, not `symbolize_keys`, following `JSON.parse(..., symbolize_names: true)`. ---------------------------------------- Feature #19591: Add symbolize_keys to MatchData#named_captures https://bugs.ruby-lang.org/issues/19591#change-102779 * Author: palkan (Vladimir Dementyev) * Status: Open * Priority: Normal ---------------------------------------- This feature is a follow-up for MatchData#deconstruct_keys (see https://github.com/ruby/ruby/pull/6216). Example: ```ruby m = /(?<a>.)(?<a>.)/.match("01") # => #<MatchData "01" a:"0" a:"1"> m.named_captures #=> {"a" => "1"} m.named_captures(symbolize_keys: true) #=> {:a => "1"} ``` The underlying (C) functionality has been already implemented. The proposal is to expose it via the optional `symbolize_keys: true | false` keyword argument. PR is attached: https://github.com/ruby/ruby/pull/6952 -- https://bugs.ruby-lang.org/

Issue #19591 has been updated by ioquatix (Samuel Williams). Status changed from Open to Closed Merged, thanks for your contribution to Ruby. ---------------------------------------- Feature #19591: Add symbolize_names to MatchData#named_captures https://bugs.ruby-lang.org/issues/19591#change-102852 * Author: palkan (Vladimir Dementyev) * Status: Closed * Priority: Normal ---------------------------------------- This feature is a follow-up for MatchData#deconstruct_keys (see https://github.com/ruby/ruby/pull/6216). Example: ```ruby m = /(?<a>.)(?<a>.)/.match("01") # => #<MatchData "01" a:"0" a:"1"> m.named_captures #=> {"a" => "1"} m.named_captures(symbolize_names: true) #=> {:a => "1"} ``` The underlying (C) functionality has been already implemented. The proposal is to expose it via the optional `symbolize_keys: true | false` keyword argument. PR is attached: https://github.com/ruby/ruby/pull/6952 -- https://bugs.ruby-lang.org/