General

Profile

ozydingo (Andrew Schwartz)

  • Login: ozydingo
  • Registered on: 01/07/2016
  • Last sign in: 04/20/2024

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 3 3

Activity

04/21/2024

02:33 PM Ruby master Misc #20441: Should passing keyword args to method_name(*) be an error?
Understanding better the role of `ruby2_keywords` is helping, thank you. It seemed to me that either way some compati... ozydingo (Andrew Schwartz)
08:47 AM Ruby master Misc #20441: Should passing keyword args to method_name(*) be an error?
Why does this conversion to a Hash occur?
I would guess for some sense of backward compatibility with gems / code ...
ozydingo (Andrew Schwartz)
08:25 AM Ruby master Misc #20441 (Closed): Should passing keyword args to method_name(*) be an error?
In the following method:
```rb
def foo(*)
super
end
```
it is apparently the intended ruby 3 behavior to ...
ozydingo (Andrew Schwartz)
08:15 AM Ruby master Bug #20440: `super` from child class duplicating a keyword argument as a positional Hash
Ok I see it now; `super` isn't passing the args as both forms, it's passing _only_ as a positional Hash. The `x: 1` i... ozydingo (Andrew Schwartz)
07:02 AM Ruby master Bug #20440: `super` from child class duplicating a keyword argument as a positional Hash
Thanks both. I understand that Ruby 3 requires explicit handling of keyword arguments. What still seems off to me is ... ozydingo (Andrew Schwartz)

04/20/2024

09:12 AM Ruby master Bug #20440: `super` from child class duplicating a keyword argument as a positional Hash
In fact it seems we can simplify this to just calling `Child.new.foo(x: 1)`; no need for the base class `foo!` method... ozydingo (Andrew Schwartz)
09:00 AM Ruby master Bug #20440 (Closed): `super` from child class duplicating a keyword argument as a positional Hash
Apologies for the verbose title, but that's the specific set of conditions that AFAICT are required to reproduce the ... ozydingo (Andrew Schwartz)

01/12/2024

02:34 PM Ruby master Bug #20180 (Closed): Inconsistent evaluation of `**{}` depending on position in array
Reproduced on ruby:3.3 docker container
The evaluation of `**{}` differs if it appears alone (evaluates as empty /...
ozydingo (Andrew Schwartz)

03/08/2016

02:26 AM Ruby master Bug #10708: In a function call, double splat of an empty hash still calls the function with an argument
Adding to this, the current behavior results in the following inconsistent behavior: I can call an argless method usi... ozydingo (Andrew Schwartz)

01/07/2016

02:34 AM Ruby master Bug #8316: Can't pass hash to first positional argument; hash interpreted as keyword arguments
This is unfortunately still an issue with default values in positional arguments:
2.2.2 > def foo(hash={}, opt: tr...
ozydingo (Andrew Schwartz)

Also available in: Atom