I agree that `{ {a: 1} }` and `{{a: 1}}` in my suggested syntax is difficult to disambiguate. The magic inside the Ruby parser that can separate the differences as they are today must be very mind bogglingly difficult. If it were possibl...hcatlin (Hampton Catlin)
During my 15 years of Ruby programming, I can't remember a single time that the difference between string-and-symbol with regards to Hashes was used on purpose. Instead, it's the source of countless bugs, extra type checking code, and ...hcatlin (Hampton Catlin)
That's such a kind of.... odd opinion to me. I've been doing ruby for 10 years, and I still have to write fairly obvious handling code when building programming interfaces and libraries... over and over again. I guess I just see 95% of H...hcatlin (Hampton Catlin)
It was pointed out to me, that there is an ambiguity in the following case. ~~~ array.method {{a: 1}} # could be array.method { {a: 1} } #or #array.method(Map.new({a: 1})) ~~~ To be fair, I feel that this would be an extremel...hcatlin (Hampton Catlin)
Sorry, forgot to add that the literal syntax would support all currently supported string-key variations that Hash does... ~~~ {{"a" => true}} {{a: true}} {{:a => true}} ~~~ Map.new would merge in standard Hashes string keys, u...hcatlin (Hampton Catlin)
Hash is one of the best features of Ruby. I remember being so pleased when I first learned Ruby to find out that *anything* could be a key and that you could do some really clever things with scripts, if you key of non-traditional elemen...hcatlin (Hampton Catlin)
hcatlin (Hampton Catlin)01:31 PM Ruby Feature #11882: Map or NamedMap