search for: recyle0

...modate everybody's taste. That doesn't sound like an easy task ;-) I'll just reiterate my earlier comment that controlling the collapse operation via an argument named 'recycle0' doesn't make sense (collapse involves NO recycling). So I don't know if the current 'recyle0=TRUE' behavior is "the correct one" but at the very least the name of the argument is a misnomer and misleading. More generally speaking using the same argument to control 2 distinct operations is not good API design. A better design is to use 2 arguments. Then the 2 arguments ca...

On 5/24/20 00:26, Gabriel Becker wrote: > > > On Sat, May 23, 2020 at 9:59 PM Herv? Pag?s <hpages at fredhutch.org > <mailto:hpages at fredhutch.org>> wrote: > > On 5/23/20 17:45, Gabriel Becker wrote: > > Maybe my intuition is just > > different?but when I collapse multiple character vectors together, I > > expect?all the

...doesn't sound like an easy task ;-) > I'll just reiterate my earlier comment that controlling > the collapse operation via an argument named 'recycle0' > doesn't make sense (collapse involves NO recycling). So I > don't know if the current 'recyle0=TRUE' behavior is "the > correct one" but at the very least the name of the > argument is a misnomer and misleading. > More generally speaking using the same argument to control > 2 distinct operations is not good API design. A better > design is to...

...e behavior should be different than now, and should either error (possibly, by Gabe), or return a single string (possibly with a warning), i.e., collapse = <string> behavior should not be influenced (or possibly be conflicting with) by recycle0=TRUE. Within R core, some believe the current recyle0=TRUE behavior to be the correct one. Personally, I see reasons for both.. What about remaining back-compatible, not only to R 3.y.z with default recycle0=FALSE, but also to R 4.0.0 with recycle0=TRUE *and* add a new option for the Suharto-Bill-Herv?-Gabe behavior, e.g., recycle0="sep.only&qu...