From: duerst@... Date: 2019-06-16T03:04:06+00:00 Subject: [ruby-core:93171] [Ruby trunk Feature#15927] Allow string keys to be used for String#% and sprintf methods Issue #15927 has been updated by duerst (Martin D�rst). I agree with @sawa that there's a difference between gsub (where strings are replaced by strings) and sprintf, where it's interpolating something very close to variables. A use case such as ``` "foo = %{foo}" % { 'foo' => 'bar' } ``` can just be rewritten to ``` "foo = %{foo}" % { foo: 'bar' } ``` Can you give us some actual use case(s) where such rewriting would not be possible, or very tedious? ---------------------------------------- Feature #15927: Allow string keys to be used for String#% and sprintf methods https://bugs.ruby-lang.org/issues/15927#change-78612 * Author: luke-gru (Luke Gruber) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- Right now, in the methods sprintf() and String#%, only symbol keys can be used for named interpolation. For example (from the example documentation): "foo = %{foo}" % { :foo => 'bar' } #=> "foo = bar" String keys do not work like this: "foo = %{foo}" % { 'foo' => 'bar' } #=> raises KeyError I think string keys should work just the same as symbol keys here. I've created a PR on github for this, perhaps misguidedly, but if can be found here: https://github.com/ruby/ruby/pull/2238 My argument for this feature is that String#gsub() and family works with string keys if given a Hash, for example: "chocolate ice cream".gsub(/\bc/, { 'c' => 'C' }) #=> 'Chocolate ice Cream' Also, I don't like having to symbolize keys in strings unnecessarily, but maybe that just goes back to when Ruby couldn't GC some symbols. -- https://bugs.ruby-lang.org/ Unsubscribe: