@duerst When final number of permutations is small - there is no problem materialising all of them and joining in one array using `flat_map`, but when number of permutations/combinations is big and there is no need to get all results in ...toy (Ivan Kuchin)
@nobu I was not sure what to select, Enumerable or multiple arguments, changed the proposal to use multiple arguments @mame I've added few use casestoy (Ivan Kuchin)
When using functions `permutation`, `repeated_permutation`, `combination` and `repeated_combination`, often one needs not one, but multiple permutation/combination sizes. Currently all functions accept one Integer argument (for `permutat...toy (Ivan Kuchin)
If method is passing arguments using `...`, then receiver visibility gets ignored if once called without receiver: ```ruby class A private def foo = :foo def bar = :bar end class B def initialize(o) @o = o end...toy (Ivan Kuchin)
The problem was noticed in code that is boiled down to: ```ruby # encoding: UTF-8 str = "something" p str.encoding # => #<Encoding:UTF-8> p [nil, str].join.encoding # => #<Encoding:US-ASCII> ``` As `nil.to_s` is an empty str...toy (Ivan Kuchin)
nobu (Nobuyoshi Nakada) wrote in #note-1: > As for this name, I’m not sure if it is appropriate, though. Few more ideas for the name: ```rb # to not explicitly use word "map" if it feels confusing find_mapped find_transform fi...toy (Ivan Kuchin)
I would like to retry proposing method `Array#find_map` that was rejected in [8421](https://bugs.ruby-lang.org/issues/8421) which happened before introduction of `filter_map` in [15323](https://bugs.ruby-lang.org/issues/15323). It would...toy (Ivan Kuchin)
`Array` and `Hash` have matching methods to fetch: * One value using `[]` (`Array` also allows fetching multiple with range or two arguments) * One value with default or exception using `fetch` method * Multiple values using `values...toy (Ivan Kuchin)
I wasn't able to reproduce segmentation fault, but even if segmentation fault is caused by `Marshal`, it doesn't explain lost messages (when `Ractor.select` returns a ractor and `"message got lost"`).toy (Ivan Kuchin)
I stumbled upon loss of messages with exceptions or even Segmentation fault during transfer of exception from Ractor when moving the exception. In versions 3.0 and 3.1 I saw only loss of messages, in 3.2 also Segmentation fault. Loss of ...toy (Ivan Kuchin)