search for: endomorphic

...f(x, ...) Except, perhaps, in terms of when the promise for 'x' gets forced. We shouldn't need to mess with bindings in environments to make that work. My understanding is that the '.' placeholder is used so that the magrittr pipe can be adapted to functions that aren't endomorphic or otherwise easily pipeable. I would argue that: 1. Users could just create their own pipable wrapper functions if so required, or 2. Users could use magrittr to get some of the 'extensions' to the pipe operator (with the noted caveats). Best, Kevin [[alternative HTML version deleted]]

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

...see to > having people just use the package version. > > Sure it may be a little weird, but it doesn't ever really stop the > people from using it or present a significant barrier. Another major point > is that many (most?) base R functions are not necessarily tooled to be > endomorphic, which in my personal opinion is *largely* 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 mit...

...see to > having people just use the package version. > > Sure it may be a little weird, but it doesn't ever really stop the > people from using it or present a significant barrier. Another major point > is that many (most?) base R functions are not necessarily tooled to be > endomorphic, which in my personal opinion is *largely* 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 mit...

...lly any major downsides that I see to having people just use the package version. Sure it may be a little weird, but it doesn't ever really stop the people from using it or present a significant barrier. Another major point is that many (most?) base R functions are not necessarily tooled to be endomorphic, which in my personal opinion is *largely* 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...

...3 and S4 generic: #' Subset method for a LongTable object. #' #' Allows use of the colData and rowData `data.table` objects to query based on #' rowID and colID, which is then used to subset all value data.tables stored #' in the dataList slot. #' #' This function is endomorphic, it always returns a LongTable object. #' #' @param x [`LongTable`] The object to subset. #' @param rowQuery [`character`, `numeric`, `logical` or `expression`] #' Character: pass in a character vector of drug names, which will subset the #' object on all row id columns ma...

...people just use the package version. >> >> Sure it may be a little weird, but it doesn't ever really stop the >> people from using it or present a significant barrier. Another major point >> is that many (most?) base R functions are not necessarily tooled to be >> endomorphic, which in my personal opinion is *largely* 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 t...

...I see to > having people just use the package version. > > Sure it may be a little weird, but it doesn't ever really stop the > people from using it or present a significant barrier. Another major point > is that many (most?) base R functions are not necessarily tooled to be > endomorphic, which in my personal opinion is *largely* 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 miti...

> On 7 Oct 2019, at 17:04, Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > Think about what happens if an > argument in a pipe stage contains a pipe. (Not completely > unreasonable, e.g. for a left_join). It should work exactly as it does in a local environment. ``` `%foo%` <- function(x, y) { env <- parent.frame() # Use `:=` to avoid partial matching on

...people just use the package version. >> >> Sure it may be a little weird, but it doesn't ever really stop the >> people from using it or present a significant barrier. Another major point >> is that many (most?) base R functions are not necessarily tooled to be >> endomorphic, which in my personal opinion is *largely* 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 t...

...re extensive definitions of "space", such as including Unicode spaces (as wished in PR#17431). * weighted.mean() no longer coerces the weights to a double/numeric vector, since sum() now handles integer overflow. This makes weighted.mean() more polymorphic and endomorphic, but be aware that the results are no longer guaranteed to be a vector of type double. * When loading namespaces, S3 method registrations which overwrite previous registrations are now noted by default (using packageStartupMessage()). * compiler::cmpfile() gains a...

...re extensive definitions of "space", such as including Unicode spaces (as wished in PR#17431). * weighted.mean() no longer coerces the weights to a double/numeric vector, since sum() now handles integer overflow. This makes weighted.mean() more polymorphic and endomorphic, but be aware that the results are no longer guaranteed to be a vector of type double. * When loading namespaces, S3 method registrations which overwrite previous registrations are now noted by default (using packageStartupMessage()). * compiler::cmpfile() gains a...

...re extensive definitions of "space", such as including Unicode spaces (as wished in PR#17431). * weighted.mean() no longer coerces the weights to a double/numeric vector, since sum() now handles integer overflow. This makes weighted.mean() more polymorphic and endomorphic, but be aware that the results are no longer guaranteed to be a vector of type double. * When loading namespaces, S3 method registrations which overwrite previous registrations are now noted by default (using packageStartupMessage()). * compiler::cmpfile() gains a...