[#118415] [Ruby master Bug#20601] Configuration flags are not properly propagated to assembler — "vo.x (Vit Ondruch) via ruby-core" <ruby-core@...>

Issue #20601 has been reported by vo.x (Vit Ondruch).

7 messages 2024/07/02

[#118467] [Ruby master Feature#20610] Float::INFINITY as IO.select timeout argument — "akr (Akira Tanaka) via ruby-core" <ruby-core@...>

Issue #20610 has been reported by akr (Akira Tanaka).

8 messages 2024/07/07

[#118483] [Ruby master Bug#20614] Integer#size returns incorrect values on 64-bit Windows — surusek via ruby-core <ruby-core@...>

SXNzdWUgIzIwNjE0IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IHN1cnVzZWsgKMWBdWthc3ogU3VyKS4N

10 messages 2024/07/08

[#118577] [Ruby master Bug#20631] Build failure with Xcode 16 beta and macOS 15 (Sequoia) Beta — "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>

Issue #20631 has been reported by hsbt (Hiroshi SHIBATA).

9 messages 2024/07/12

[#118682] [Ruby master Misc#20652] Memory allocation for gsub has increased from Ruby 2.7 to 3.3 — "orisano (Nao Yonashiro) via ruby-core" <ruby-core@...>

Issue #20652 has been reported by orisano (Nao Yonashiro).

28 messages 2024/07/25

[ruby-core:118508] [Ruby master Bug#20570] Nokey behavior changed since 3.3.

From: "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@...>
Date: 2024-07-08 23:09:37 UTC
List: ruby-core #118508
Issue #20570 has been updated by k0kubun (Takashi Kokubun).


I _think_ I managed to fix the conflict. I'd appreciate a backport PR next time though.

----------------------------------------
Bug #20570: Nokey behavior changed since 3.3.
https://bugs.ruby-lang.org/issues/20570#change-109030

* Author: ksss (Yuki Kurihara)
* Status: Closed
* Assignee: ko1 (Koichi Sasada)
* ruby -v: ruby 3.3.2 (2024-05-30 revision e5a195edf6) [arm64-darwin22]
* Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: REQUIRED
----------------------------------------
I am using code that transfers the following method call, but found that the behavior has changed since CRuby 3.3.

```ruby
receiver_value = Set.new
method_name = :merge
args = [1]
kwargs = {}
block = nil
receiver_value.__send__(method_name, *args, **kwargs, &block)
# => no keywords accepted (ArgumentError)
```

Upon investigation, I found that the behavior of calling a method using `**nil` has changed starting from version 3.3.

```
$ docker run -it --rm rubylang/all-ruby env ALL_RUBY_SINCE=ruby-2.6 ./all-ruby -e 'def foo(*, **nil); end; p foo(*[], **{})'
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
ruby-2.6.0          -e:1: syntax error, unexpected nil, expecting ')'
                    def foo(*, **nil); end; p foo(*[], **{})
                                 ^~~
                exit 1
...
ruby-2.6.10         -e:1: syntax error, unexpected nil, expecting ')'
                    def foo(*, **nil); end; p foo(*[], **{})
                                 ^~~
                exit 1
ruby-2.7.0-preview1 -e:1: syntax error, unexpected `nil', expecting ')'
                    def foo(*, **nil); end; p foo(*[], **{})
                                 ^~~
                exit 1
ruby-2.7.0-preview2 nil
...
ruby-3.2.4          nil
ruby-3.3.0-preview1 -e:1:in `<main>': no keywords accepted (ArgumentError)

                    def foo(*, **nil); end; p foo(*[], **{})
                                                  ^^^^^^^^^
                exit 1
...
ruby-3.3.2          -e:1:in `<main>': no keywords accepted (ArgumentError)

                    def foo(*, **nil); end; p foo(*[], **{})
                                                  ^^^^^^^^^
                exit 1
ruby-3.4.0-preview1 -e:1:in '<main>': no keywords accepted (ArgumentError)

                    def foo(*, **nil); end; p foo(*[], **{})
                                                  ^^^^^^^^^
                exit 1
```

Is this change intentional?



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/


In This Thread