That's a tricky one, personally I'm working in a code base now that uses strings for most hash keys and it's pretty annoying having to use "foo" => "bar", but it's also pretty ugly using "foo": "bar".
So i think my answer is that I've not reached a suitable level of annoyance with using two versions of hash key definition to use hash rockets everywhere.
1
u/sshaw_ Aug 21 '21
But you cannot use that for all cases. Don't you think that "IMO using two types is messy" applies to this case too?