[#103241] [Ruby master Bug#17777] 2.6.7 fails to build on macOS: implicit declaration of function 'rb_native_mutex_destroy' is invalid in C99 — eregontp@...
Issue #17777 has been reported by Eregon (Benoit Daloze).
17 messages
2021/04/05
[#103305] [Ruby master Feature#17785] Allow named parameters to be keywords — marcandre-ruby-core@...
Issue #17785 has been reported by marcandre (Marc-Andre Lafortune).
21 messages
2021/04/08
[#103342] [Ruby master Feature#17790] Have a way to clear a String without resetting its capacity — jean.boussier@...
Issue #17790 has been reported by byroot (Jean Boussier).
14 messages
2021/04/09
[#103388] [ANN] Multi-factor Authentication of bugs.ruby-lang.org — SHIBATA Hiroshi <hsbt@...>
Hello,
5 messages
2021/04/12
[#103414] Re: [ANN] Multi-factor Authentication of bugs.ruby-lang.org
— Martin J. Dürst <duerst@...>
2021/04/13
Is there a way to use this multi-factor authentication for (like me)
[#103547] List of CI sites to check — Martin J. Dürst <duerst@...>
Hello everybody,
4 messages
2021/04/22
[#103596] [Ruby master Feature#17830] Add Integer#previous and Integer#prev — rafasoaresms@...
Issue #17830 has been reported by rafasoares (Rafael Soares).
9 messages
2021/04/26
[ruby-core:103368] [Ruby master Feature#17785] Allow named parameters to be keywords
From:
jean.boussier@...
Date:
2021-04-10 07:47:29 UTC
List:
ruby-core #103368
Issue #17785 has been updated by byroot (Jean Boussier).
> the number of keywords is very low, which means that the cases where using a keyword as an argument name makes sense is also very low.
Variable and keyword names are not purely random though, so I don't think this statistical reasoning makes that much sense. Especially since keywords reserved names that are short and popular: `end`, `class`, etc. If you define method that generate some HTML, a `class:` named parameters is common, if you define a method that deal with period of times, `end:` is common, `if:` is common for methods taking callbacks, etc.
I'm not for adding extra syntax, but I agree with @marcandree that `binding.local_variable_get(:class)` is too slow to be used in many cases.
It would be great if the parser or VM would just optimize it away, but I understand that it's currently very tricky because both `#binding` and `Binding#local_variable_get` could have been redefined.
----------------------------------------
Feature #17785: Allow named parameters to be keywords
https://bugs.ruby-lang.org/issues/17785#change-91461
* Author: marcandre (Marc-Andre Lafortune)
* Status: Open
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
----------------------------------------
We should allow named parameters to be keywords and use add a trailing `_` to the corresponding variable:
```ruby
def check(arg, class:)
arg.is_a?(class_)
end
check(42, class: Integer) # => true
```
Currently, if we want such an API we have to use `**rest`:
```ruby
def check(arg, **rest)
class_ = rest.fetch(:class) { raise ArgumentError('missing keyword: :class')}
if rest.size > 1
unknown = rest.keys - [:class]
raise ArgumentError("unknown keyword(s): :#{unknown.join(', :')})
end
arg.is_a?(class_)
end
```
This is very verbose, much less convenient, much less readable, prevents `steep` from generating the proper signature, etc.
We should do the same for pattern match.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>