Eregon (Benoit Daloze) wrote in #note-40: > With the example from @mame, I think adding `(&)` or `(&on_missing)` for `Attribute::Attribute#value` would be good to clarify the value method can receive a block, and purposefully ignores it...matthewd (Matthew Draper)
If the supplied hash is already frozen and compare-by-identity, we can use it directly (still checking its contents are valid symbols), without making a new copy.matthewd (Matthew Draper)
When interrupt behavior is configured for all possible exceptions using 'Exception', there's no need to iterate the pending exception's ancestors for hash lookups. More significantly, by storing the catch-all timing symbol directly in t...matthewd (Matthew Draper)
Teach getblockparamproxy to handle the no-block case without exiting Co-authored-by: John Hawthorn <john@hawthorn.email> Co-authored-by: John Hawthorn <john@hawthorn.email>matthewd (Matthew Draper)
The trouble with using `send` in this [general] situation is that it makes it too equally-easy to reach into _all_ internals: you want access to methods that are suitable for a collaborator but not a downstream user, but you can also imm...matthewd (Matthew Draper)
> Calling "private/protected" methods on another object feels rather wrong to me. The whole point of `protected` is that it allows you to call methods on another object. But I assume you meant another object that is not an instance of...matthewd (Matthew Draper)
> Over 80% of CRuby's base startup is due to eagerly booting RubyGems. We can do better! It's not the main point here, but perhaps still worth noting: `--disable-gems` implies `--disable=error_highlight,did_you_mean`. In my own brief l...matthewd (Matthew Draper)
This is great! Ignored blocks can be very confusing. > A method called by super doesnt warn warning even if this method doesn't use a block. > ... Would it be possible for a method called by `super` to only ignore an unexpected block...matthewd (Matthew Draper)
This is excellent news indeed! Do you think a similar technique could work for passing along `*args` in the future? It would be great if simple delegation could get a similar gain by going zero-allocation: ~~~ def goal a, b ...matthewd (Matthew Draper)
matthewd (Matthew Draper)06:58 AM Ruby Feature #15554: warn/error passing a block to a method which never use a block