wojtekmach (Wojtek Mach)
- Login: wojtekmach
- Email: wojtek@wojtekmach.pl
- Registered on: 07/08/2014
- Last sign in: 08/13/2015
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
06/02/2015
-
09:42 PM Ruby Feature #10017: Add `Hash#fetch_values`
- Hi, please let me know if there's anything I can do to move this ticket forward.
12/03/2014
-
09:49 PM Ruby Feature #10017: Add `Hash#fetch_values`
- I submitted PR for this change: https://github.com/ruby/ruby/pull/776 calling the method `fetch_values`.
10/13/2014
-
10:10 AM Ruby Feature #10017: Add `Hash#fetch_values`
- Should we get some more votes here, or should I just change my patch to use fetch_values?
07/24/2014
-
08:42 PM Ruby Feature #10017: Add `Hash#fetch_values`
- Andrew Vit wrote:
> Please consider the name `fetch_at` carefully: it seems easily confused with `fetch` (1 key), and the name doesn't hint that it's for multiple keys. (`values_at` is plural, so it gives a good clue.) Maybe `fetch_valu...
07/09/2014
-
07:00 PM Ruby Feature #10017: Add `Hash#fetch_values`
- I attached another patch calling this method fetch_at and I also added missing tests (I couldn't change issue title & body to reflect this changes, though).
Also, perhaps out of scope for this ticket but I'm wondering what're your tho...
07/08/2014
-
10:37 PM Ruby Feature #10017 (Closed): Add `Hash#fetch_values`
- I'm proposing to add a new method `Hash#values_at!` that's basically a combination of `#values_at` and `#fetch`.
When dealing with configuration I prefer to use `#fetch` to fail early and this would be useful to read multiple keys at ...