ruby-dev December 2022

ruby-dev@ml.ruby-lang.org

2 participants
13 discussions

[ruby-dev:52010] [Ruby master Feature#19134] ** is not allowed in def foo(...)

by Eregon (Benoit Daloze)

Issue #19134 has been updated by Eregon (Benoit Daloze). Although, it should still be possible to optimize delegation as good as possible and allow `*`/`**`/`&` by having those behave like `def args(*,**,&) = *`, `def kwargs(*,**,&) = **`, `def block(*,**,&) = &` and as if `*` was replaced by `args(...)`, etc, but that's of course at the expense of making the handling of those slightly slower and more complicated (but at least it doesn't slow down delegation via `(...)`). ---------------------------------------- Feature #19134: ** is not allowed in def foo(...) https://bugs.ruby-lang.org/issues/19134#change-100489 * 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 year, 4 months

[ruby-dev:52009] [Ruby master Feature#19134] ** is not allowed in def foo(...)

by Eregon (Benoit Daloze)

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 year, 4 months

[ruby-dev:52007] [Ruby master Feature#19163] Data object should be frozen

by matz (Yukihiro Matsumoto)

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/

1 year, 5 months

2024

2023

2022

ruby-dev December 2022