apotonick (Nick Sutterer)
- Login: apotonick
- Email: apotonick@gmail.com
- Registered on: 10/30/2012
- Last sign in: 12/02/2025
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 3 | 3 |
Activity
12/02/2025
-
04:26 PM Ruby Bug #21757 (Closed): Splatted args array is mutated when passing unexpected kwargs
- The bug is very simple to provoke.
``` ruby
proc = ->(*) { } # we do NOT expect any keyword arguments.
args = [1, 2]
proc.(*args, bug: true)
pp args #=> [1, 2, {bug: true}]
```
The `args` array now has a third element ...
03/14/2018
-
03:05 PM Ruby Feature #14603 (Closed): Better error message when double-splatting hash with string keys
- I couldn't find an existing issue even though I remember reading about it somewhere.
When double-splatting a hash with string keys, the error message is very cryptic.
~~~ ruby
a( **{ "key" => 1} )
#=> TypeError (wrong argument ...
10/31/2012
-
07:45 PM Ruby Feature #7240: Inheritable #included/#extended Hooks For Modules
- =begin
Ah ok, now I understand you, Alexey. Instead of having a keyword (inclusive/inheritable) you want to have a special "namespace" as in
module M
def to_be_inherited.m; end
which would include the class method #m when includi... -
07:01 PM Ruby Feature #7240: Inheritable #included/#extended Hooks For Modules
- =begin
Interesting points, mates. I don't know about the method tables so all I can do is summarizing what we came up with so far.
== 1. Explicitely define inheritable class methods.
module M
inclusive/inheritable
def self.i_wi...
10/30/2012
-
07:08 AM Ruby Feature #7240 (Feedback): Inheritable #included/#extended Hooks For Modules
- An inheritable hook mechanism for modules would be a great way for module/gem authors to simplify their implementations.
The Problem
-----------
Let's say I have the following module.
module A
def self.included(base)
...