search for: debuggi

Yes but this exageration precisely misses the point. Concerning your examples: * I love fread but I think it makes a lot of subjective choices that are best associated with a package. I think it changed a lot with time and can still change, and we have great developers willing to maintain it and be reactive regarding feature requests or bug reports *.group_by() adds a class that works only (or

...t; the pipes are really compelling. > > That was for pipes as the exist in package space, though. There is another > way the pipe could go into base R that could not be done in package space > and has the potential to mitigate some pretty serious downsides to the > pipes relating to debugging, which would be to implement them in the parser. Actually, that could be done in package space too: just write a function to do the transformation. That is, something like transformPipe( a %>% b %>% c ) could convert the original expression into one like yours below. This could...

Hi Gabe, > There is another way the pipe could go into base R that could not be > done in package space and has the potential to mitigate some pretty > serious downsides to the pipes relating to debugging I assume you're thinking about the large stack trace of the magrittr pipe? You don't need a parser transformation to solve this problem though, the pipe could be implemented as a regular function with a very limited impact on the stack. And if implemented as a SPECIALSXP, it would be com...

...argely* the only place that the pipes are really compelling. That was for pipes as the exist in package space, though. There is another way the pipe could go into base R that could not be done in package space and has the potential to mitigate some pretty serious downsides to the pipes relating to debugging, which would be to implement them in the parser. If iris %>% group_by(Species) %>% summarize(mean_sl = mean(Sepal.Length)) %>% filter(mean_sl > 5) were *parsed* as, for example, into local({ . = group_by(iris, Species) ._tmp2 = summarize(., mean_sl = mean...

On 07/10/2019 4:22 a.m., Lionel Henry wrote: > Hi Gabe, > >> There is another way the pipe could go into base R that could not be >> done in package space and has the potential to mitigate some pretty >> serious downsides to the pipes relating to debugging > > I assume you're thinking about the large stack trace of the magrittr > pipe? You don't need a parser transformation to solve this problem > though, the pipe could be implemented as a regular function with a > very limited impact on the stack. And if implemented as a SP...

...gt; the pipes are really compelling. > > That was for pipes as the exist in package space, though. There is another > way the pipe could go into base R that could not be done in package space > and has the potential to mitigate some pretty serious downsides to the > pipes relating to debugging, which would be to implement them in the > parser. > > If > > iris %>% group_by(Species) %>% summarize(mean_sl = mean(Sepal.Length)) %>% > filter(mean_sl > 5) > > > were *parsed* as, for example, into > > local({ > . = group_by(iris, Spe...

On Mon, 7 Oct 2019, Lionel Henry wrote: > Hi Gabe, > >> There is another way the pipe could go into base R that could not be >> done in package space and has the potential to mitigate some pretty >> serious downsides to the pipes relating to debugging > > I assume you're thinking about the large stack trace of the magrittr > pipe? You don't need a parser transformation to solve this problem > though, the pipe could be implemented as a regular function with a > very limited impact on the stack. And if implemented as a SPE...