From: merch-redmine@... Date: 2020-02-20T00:04:51+00:00 Subject: [ruby-core:97205] [Ruby master Bug#16642] Splatted empty hash literal produces frozen hash object Issue #16642 has been updated by jeremyevans0 (Jeremy Evans). I agree it is a bug. I'm not sure it is worth fixing. Basically, the reason behind it is the parser doesn't separate hash compilation from keyword argument compilation, and the optimization for `**{}` as the only keyword argument ends up applying to hashes as well. It is simple to remove the optimization, but it will result in worse performance for keyword arguments using `**{}` (which can be used to avoid keyword argument warnings in Ruby 2.7). Separate parsing and/or compilation of keyword arguments and hashes will fix this, and it is on my todo list. ---------------------------------------- Bug #16642: Splatted empty hash literal produces frozen hash object https://bugs.ruby-lang.org/issues/16642#change-84313 * Author: Dan0042 (Daniel DeLorme) * Status: Open * Priority: Normal * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- When splatting an empty hash literal, internally it's optimized using a global frozen hash object, but this implementation detail can leak into the ruby code outside: ```ruby ruby2_keywords def foo(*a) a.last end h = foo(**{}) h[1] = 2 # can't modify frozen Hash: {} (FrozenError) ``` I think this can be considered a bug? -- https://bugs.ruby-lang.org/ Unsubscribe: