[ruby-core:120255] [Ruby master Feature#20953] Array#fetch_values vs #values_at protocols
From:
"byroot (Jean Boussier) via ruby-core" <ruby-core@...>
Date:
2024-12-15 23:29:11 UTC
List:
ruby-core #120255
Issue #20953 has been updated by byroot (Jean Boussier).
`Array#fetch_values` is modeled after `Hash#fetch_values`, not `Array#values_at`.
Since Array "keys" can only possibly be integers, it makes sense for a method that is specific to Array to cast the arguments this way.
But for the method that is meant to be used indiscriminately with either Array or Hash, I don't think it's a good idea.
----------------------------------------
Feature #20953: Array#fetch_values vs #values_at protocols
https://bugs.ruby-lang.org/issues/20953#change-111021
* Author: zverok (Victor Shepelev)
* Status: Open
----------------------------------------
I believe that the user might expect `#fetch_values` to be a stricter version of `#values_at`, confirming to the same protocol for arguments.
But the current implementation for `#fetch_values` is simpler:
```ruby
[1, 2, 3, 4, 5].values_at(0, 3..4) #=> [1, 4, 5]
[1, 2, 3, 4, 5].fetch_values(0, 3..4) # TypeError: in 'Array#fetch': no implicit conversion of Range into Integer
```
I believe aligning the implementations would lessen confusion (even if it makes `#fetch_values` implementation somewhat less trivial).
The practical example of usefulness:
```ruby
HEADERS = %w[Name Department]
def table_headers(rows)
HEADERS.fetch_values(...rows.map(&:size).max) { '<unknown'> }
# Or, alternatively:
# HEADERS.fetch_values(...rows.map(&:size).max) { raise ArgumentError, "No header defined for column #{it + 1}" }
end
table_headers([
['John'],
['Jane'],
]) #=> ["Name"]
table_headers([
['John'],
['Jane', 'Engineering'],
]) #=> ["Name", "Department"]
table_headers([
['John', 'Accounting', 'Feb 24'],
['Jane', 'Engineering'],
]) #=> ["Name", "Department", "<unknown>"]
# or ArgumentError No header defined for column 3
```
(Obviously, we can use `fetch_values(*(0...max_row_size))` as an argument, but it feels like an unjustified extra work when `values_at` already can do this.)
--
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/