From: "matz (Yukihiro Matsumoto) via ruby-core" <ruby-core@...>
Date: 2024-08-01T09:37:34+00:00
Subject: [ruby-core:118767] [Ruby master Feature#20508] Explicit access to *, **, &, and ...

Issue #20508 has been updated by matz (Yukihiro Matsumoto).


I am not sure why you don't want to name arguments, where simple `a`, `b`, `c` might work. Elaborate the motivation behind the proposal.
Otherwise, I am against the proposal. It does not worth the effort (and hindering the future optimization).

Matz.


----------------------------------------
Feature #20508: Explicit access to *, **, &, and ...
https://bugs.ruby-lang.org/issues/20508#change-109319

* Author: bradgessler (Brad Gessler)
* Status: Open
----------------------------------------
I find debugging and certain meta-programming tasks challenging because there's no explicit APIs for accessing certain types of arguments in Ruby.

Here's some example code:

```ruby
def splats(one, *, two: nil, **, &)
  # These work
  p(*)
  p(**)
  # But the block doesn't show a proc.
  p(&)

  # This would show [:one, :two, :_]
  p binding.local_variables
end

splats(:arg, two: true) do
  42
end
```

I'm not sure how to access the `&` variable, unless I name it. The same applies to endless ruby methods.

I'd like to see a way to explicitly call bindings for those methods. Something like this (not sure if binding is the right place for it):

```ruby
def splats(one, *, true: nil, **, &)
  binding.arguments # Returns an array
  binding.keyword_arguments # Returns a hash
  binding.block_argument # Returns a block
end
```

These methods would give me access to the values used to call the method.




-- 
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/