Comments on: Recursively Symbolize Keys http://avdi.org/devblog/2009/07/14/recursively-symbolize-keys/ "...the three great virtues of a programmer: laziness, impatience, and hubris." -- Larry Wall Wed, 03 Mar 2010 21:56:22 -0800 http://wordpress.org/?v=2.8.5 hourly 1 By: akzhan http://avdi.org/devblog/2009/07/14/recursively-symbolize-keys/comment-page-1/#comment-833 akzhan Wed, 24 Feb 2010 13:23:53 +0000 http://avdi.org/devblog/?p=213#comment-833 using each_pair is faster than inject (in my tests on ruby 1.8.7 EE. using each_pair is faster than inject (in my tests on ruby 1.8.7 EE.

]]> By: pjb3 http://avdi.org/devblog/2009/07/14/recursively-symbolize-keys/comment-page-1/#comment-666 pjb3 Tue, 21 Jul 2009 11:19:39 +0000 http://avdi.org/devblog/?p=213#comment-666 I also like to have symbolize_keys be a method on Hash rather than passing the hash to symbolize_keys, otherwise it feels like Python :)<br><br>Here it is with that and ternaries, which is a little more compact but I think still readable.<br><br><a href="http://gist.github.com/151324" rel="nofollow">http://gist.github.com/151324</a> I also like to have symbolize_keys be a method on Hash rather than passing the hash to symbolize_keys, otherwise it feels like Python :)

Here it is with that and ternaries, which is a little more compact but I think still readable.

http://gist.github.com/151324

]]> By: avdi http://avdi.org/devblog/2009/07/14/recursively-symbolize-keys/comment-page-1/#comment-665 avdi Wed, 15 Jul 2009 12:28:35 +0000 http://avdi.org/devblog/?p=213#comment-665 Yeah, I know about the symbol syntax in YAML. But a lot of YAML formats don't use it, presumably because the string syntax is more pleasant to read, and perhaps because insisting on adding the file's symbols to the system string table is arguably presumptuous. Or maybe just because it's easy to forget to type that leading colon.<br><br>A running theme in my work is solutions that don't require extending core classes, but there are certainly advantages to the module inclusion approach. Yeah, I know about the symbol syntax in YAML. But a lot of YAML formats don't use it, presumably because the string syntax is more pleasant to read, and perhaps because insisting on adding the file's symbols to the system string table is arguably presumptuous. Or maybe just because it's easy to forget to type that leading colon.

A running theme in my work is solutions that don't require extending core classes, but there are certainly advantages to the module inclusion approach.

]]> By: Botanicus http://avdi.org/devblog/2009/07/14/recursively-symbolize-keys/comment-page-1/#comment-664 Botanicus Wed, 15 Jul 2009 12:21:07 +0000 http://avdi.org/devblog/?p=213#comment-664 BTW you can also use symbols in YAML, just do something like that:<br><br>---<br>:key: value<br><br>About your example, I personally prefer to create SymbolizedKeysMixin, include it to the Hash class and use key.respond_to?(:symbolize_keys) rather than testing class of each key. So the only thing for supporting another classes will be e. g. Mash.send(:include, SymbolizedKeysMixin). BTW you can also use symbols in YAML, just do something like that:

—
:key: value

About your example, I personally prefer to create SymbolizedKeysMixin, include it to the Hash class and use key.respond_to?(:symbolize_keys) rather than testing class of each key. So the only thing for supporting another classes will be e. g. Mash.send(:include, SymbolizedKeysMixin).

]]>