Issue #19607 has been updated by janosch-x (Janosch Müller). nobu (Nobuyoshi Nakada) wrote in #note-4:
I have never needed such operation. What’s the use case?
dealing with data from uncontrolled sources, supporting multiple sources of config data (e.g. YML, JSON, code etc.), and making a less picky interface in general. some examples: - [faker interface](https://github.com/faker-ruby/faker/blob/6aae8e21e1eaf9ae845017a86c62ae44c9d...) - [pg config](https://github.com/ged/ruby-pg/blob/2e663b34745c9a91610bfb58b42cd6ecafc2331f...) - [redis config](https://github.com/redis/redis-rb/blob/4e9d73d3bb47831fe720cbce7c47cb11dd3f4...) - [solargraph interface](https://github.com/castwide/solargraph/blob/d48f3963d1ce19b369efbc7f0327b277...) - [interface in ruby/optparse](https://github.com/ruby/ruby/blob/39bbbd767d6465080c6e1d6ba0da98c2762eedc6/l...) (this is btw another precedent/occurrence of `symbolize_names` outside JSON and Psych). ---------------------------------------- Feature #19607: Introduce `Hash#symbolize_keys`. https://bugs.ruby-lang.org/issues/19607#change-102867 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- This is a very common operation. It can currently be implemented using `Hash#transform_keys(&:to_sym)`. It's currently provided by Rails as `Hash#symbolize_keys` and `Hash#symbolize_keys!`. Proposed implementation is identical to Rails implementation: https://github.com/rails/rails/blob/539144d2d61770dab66c8643e744441e52538e09... For completeness we could also consider adding `stringify_keys` but I think that's less frequently used. -- https://bugs.ruby-lang.org/