- ruby-dev - ml.ruby-lang.org

[ruby-dev:52009] [Ruby master Feature#19134] ** is not allowed in def foo(...)
by Eregon (Benoit Daloze) 04 Dec '22

04 Dec '22

Issue #19134 has been updated by Eregon (Benoit Daloze). IMHO if `...` is used then `*`, `**` and `&` should all be forbidden (a SyntaxError at parse time). Because that way is the best for optimizing delegation. And also taking apart `*` and `**` is arguably not really delegation anymore. ---------------------------------------- Feature #19134: ** is not allowed in def foo(...) https://bugs.ruby-lang.org/issues/19134#change-100486 * Author: shugo (Shugo Maeda) * Status: Closed * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- `*` and `&` are allowed in the body of a method with `...` argument forwarding, but `**` is not allowed. ``` def foo(...) bar(*) # OK baz(&) # OK quux(**) # NG end ``` Is it intended behavior? It seems that parse.y has code like `#ifdef RUBY3_KEYWORDS`, and if RUBY3_KEYWORDS, `**` will also be supported. -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52007] [Ruby master Feature#19163] Data object should be frozen
by matz (Yukihiro Matsumoto) 01 Dec '22

01 Dec '22

Issue #19163 has been reported by matz (Yukihiro Matsumoto). ---------------------------------------- Feature #19163: Data object should be frozen https://bugs.ruby-lang.org/issues/19163 * Author: matz (Yukihiro Matsumoto) * Status: Open * Priority: Normal ---------------------------------------- If we call `initialize` (via `send`), we can rewrite an existing Data object. ```ruby d=Data.define(:a, :b).new(1,2) p d #=> #<data a=1, b=2> d.send(:initialize, {a:3,b:4}) p d #=> #<data a=3, b=4> ``` Should we freeze the Data object after calling `initialize` for the first time? Matz. -- https://bugs.ruby-lang.org/

2 1

[ruby-dev:52006] [Ruby master Feature#19134] ** is not allowed in def foo(...)
by shugo (Shugo Maeda) 29 Nov '22

29 Nov '22

Issue #19134 has been updated by shugo (Shugo Maeda). matz (Yukihiro Matsumoto) wrote in #note-2: > LGTM. Thank you. I've merged it. I realized that my fix also chaged the behavior of the following code: ```ruby def foo(*, **, &) bar(...) end def bar(*args, **kw, &block) p [args, kw, block&.call] end foo(1, 2, x: 3, y: 4) { 5 } ``` My fix changed the result from `[[1, 2], {}, 5]` to `[[1, 2], {:x=>3, :y=>4}, 5]`. So `...` is now a syntax sugar of `*, **, &`. ---------------------------------------- Feature #19134: ** is not allowed in def foo(...) https://bugs.ruby-lang.org/issues/19134#change-100306 * Author: shugo (Shugo Maeda) * Status: Closed * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- `*` and `&` are allowed in the body of a method with `...` argument forwarding, but `**` is not allowed. ``` def foo(...) bar(*) # OK baz(&) # OK quux(**) # NG end ``` Is it intended behavior? It seems that parse.y has code like `#ifdef RUBY3_KEYWORDS`, and if RUBY3_KEYWORDS, `**` will also be supported. -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52005] [Ruby master Feature#6133] SSLSocketをshutdownできない
by hsbt (Hiroshi SHIBATA) 29 Nov '22

29 Nov '22

Issue #6133 has been updated by hsbt (Hiroshi SHIBATA). Assignee set to rhenium (Kazuki Yamaguchi) ---------------------------------------- Feature #6133: SSLSocketをshutdownできない https://bugs.ruby-lang.org/issues/6133#change-100303 * Author: kik (Masashi Kikuchi) * Status: Assigned * Priority: Normal * Assignee: rhenium (Kazuki Yamaguchi) ---------------------------------------- http://www.openssl.org/docs/ssl/SSL_shutdown.html に対応するメソッドがないので、送信の終わりを送れません。ただし微妙にshutdown(2)とインターフェースが違ってます。 -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52004] [Ruby master Feature#19134] ** is not allowed in def foo(...)
by matz (Yukihiro Matsumoto) 28 Nov '22

28 Nov '22

Issue #19134 has been updated by matz (Yukihiro Matsumoto). LGTM. Matz. ---------------------------------------- Feature #19134: ** is not allowed in def foo(...) https://bugs.ruby-lang.org/issues/19134#change-100293 * Author: shugo (Shugo Maeda) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- `*` and `&` are allowed in the body of a method with `...` argument forwarding, but `**` is not allowed. ``` def foo(...) bar(*) # OK baz(&) # OK quux(**) # NG end ``` Is it intended behavior? It seems that parse.y has code like `#ifdef RUBY3_KEYWORDS`, and if RUBY3_KEYWORDS, `**` will also be supported. -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52003] [Ruby master Feature#19134] ** is not allowed in def foo(...)
by shugo (Shugo Maeda) 28 Nov '22

28 Nov '22

Issue #19134 has been updated by shugo (Shugo Maeda). I've created a pull request: https://github.com/ruby/ruby/pull/6818 With this change a test of rbs.gem fails because argument types of` def foo(...)` is changed to `(*untyped, **untyped **)` from `(*untyped)`, but I believe it's right. (however, the specifal variable name `**` should be hidden by rbs.gem.) I've created a issue: https://github.com/ruby/rbs/issues/1163 ---------------------------------------- Feature #19134: ** is not allowed in def foo(...) https://bugs.ruby-lang.org/issues/19134#change-100289 * Author: shugo (Shugo Maeda) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- `*` and `&` are allowed in the body of a method with `...` argument forwarding, but `**` is not allowed. ``` def foo(...) bar(*) # OK baz(&) # OK quux(**) # NG end ``` Is it intended behavior? It seems that parse.y has code like `#ifdef RUBY3_KEYWORDS`, and if RUBY3_KEYWORDS, `**` will also be supported. -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52001] [Ruby master Bug#19151] Integration test
by hsbt (Hiroshi SHIBATA) 25 Nov '22

25 Nov '22

Issue #19151 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #19151: Integration test https://bugs.ruby-lang.org/issues/19151 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- This issue is posting test for ruby-dev. -- https://bugs.ruby-lang.org/

1 1

[ruby-dev:52000] テスト送信
by SHIBATA Hiroshi 25 Nov '22

25 Nov '22

これはテストです。

1 0

[ruby-dev] Please verify your email forwarding address
by Google Domains 25 Nov '22

25 Nov '22

Google Domains <https://notifications.google.com/g/p/ACnX6LbkqHFJiT7E6LahsVBBZutwojMuiOmlAj…> ----- You recently added email forwarding from ruby-dev(a)ruby-lang.org to ruby-dev(a)ml.ruby-lang.org Verify my email now <https://notifications.google.com/g/p/ACnX6LbPiPgpXPP5Ju2YF_Xb1jeqiB9xJybAQJ…> ----- Please verify your email address to start getting emails sent to ruby-dev(a)ml.ruby-lang.org. See you online, Google Domains Team ----- Have a question? Visit the Help Center <https://notifications.google.com/g/p/ACnX6LbHTE1boZx57NANlpI8dG98HXHgO5Z9xV…> ----- Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 This email was sent to ruby-dev(a)ml.ruby-lang.org to update you about important information regarding your Google Domains account. Questions, comments, and support for Google Domains are available <https://notifications.google.com/g/p/ACnX6LaNNLfd-3QFbibYXxlyrUoL9UkaKfp3eY…>here.

1 0