search for: magrittrs

Dear R-devel, The most popular piping operator sits in the package `magrittr` and is used by a huge amount of users, and imported /reexported by more and more packages too. Many workflows don't even make much sense without pipes nowadays, so the examples in the doc will use pipes, as do the README, vignettes etc. I believe base R could have a piping operator so packages can use a pipe in

It says that nser requires the most recent version of magrittr that you do not have installed. You must update magrittr before attempting to install nser: update.packages(oldPkgs = "magrittr") or at the prompt you were presented before, choose to update magrittr before installing nser. On Sun, Apr 9, 2023, 17:55 akshay kulkarni <akshay_e4 at hotmail.com> wrote: > Dear

Dear colleagues, preparing a release of my package ?polmineR? I encountered the following issue with a new warning issued when running R CMD check with the --as-cran option on Debian with R-devel. To reexport the magrittr pipe operator %>%, my package adopted I snippet you?d see in the dplyr package, for instance: #' @importFrom magrittr %>% #' @export magrittr::`%>%` The

library("lintr") Error: package or namespace load failed for 'lintr' in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]): there is no package called 'magrittr' library("magrittr") Error in library("magrittr") : there is no package called 'magrittr' session.Info(): R version 3.4.4 (2018-03-15) Platform:

...John Mount <jmount at win-vector.com> a ?crit : > Actually, base R already has a pipe fairly close to the one you describe: > ->.; > > iris ->.; head(.) ->.; dim(.) > # [1] 6 5 > > I've called it the Bizarro pipe ( > http://www.win-vector.com/blog/2016/12/magrittrs-doppelganger/ ), and for > some reason we chickened out and didn't spend time on it in the dot pipe > paper ( https://journal.r-project.org/archive/2018/RJ-2018-042/index.html > ). > > For documentation Bizarro pipe has the advantage that one can work out how > it works from...

Dear members, I can't install "nser" package. It is not in cran but install_version and install_github both are not working: > install_version("nser",version = "1.4.0") Downloading package from url: https://cran.rstudio.com//src/contrib/Archive/nser/nser_1.4.0.tar.gz These packages have more recent versions available. It is

Actually, base R already has a pipe fairly close to the one you describe: ->.; iris ->.; head(.) ->.; dim(.) # [1] 6 5 I've called it the Bizarro pipe ( http://www.win-vector.com/blog/2016/12/magrittrs-doppelganger/ <http://www.win-vector.com/blog/2016/12/magrittrs-doppelganger/> ), and for some reason we chickened out and didn't spend time on it in the dot pipe paper ( https://journal.r-project.org/archive/2018/RJ-2018-042/index.html <https://journal.r-project.org/archive/2018/RJ-20...

IMHO, if base R were to include a pipe operator, I think it should be much simpler than the magrittr pipe. It should satisfy the property that: x |> f(...) is equivalent to 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 '.'

On 05/10/2019 7:50 p.m., Gabriel Becker wrote: > Hi all, > > I think there's some nuance here that makes makes me agree partially with > each "side". > > The pipe is inarguably extremely popular. Many probably think of it as a > core feature of R, along with the tidyverse that (as was pointed out) > largely surrounds it and drives its popularity. Whether its

...om> a ?crit : > >> Actually, base R already has a pipe fairly close to the one you describe: >> ->.; >> >> iris ->.; head(.) ->.; dim(.) >> # [1] 6 5 >> >> I've called it the Bizarro pipe ( >> http://www.win-vector.com/blog/2016/12/magrittrs-doppelganger/ ), and for >> some reason we chickened out and didn't spend time on it in the dot pipe >> paper ( https://journal.r-project.org/archive/2018/RJ-2018-042/index.html >> ). >> >> For documentation Bizarro pipe has the advantage that one can work out ho...

On Sat, 5 Oct 2019 at 17:15, Hugh Marera <hugh.marera at gmail.com> wrote: > > How is your argument different to, say, "Should dplyr or data.table be > part of base R as they are the most popular data science packages and they > are used by a large number of users?" Two packages with many features, dozens of functions and under heavy development to fix bugs, add new

How is your argument different to, say, "Should dplyr or data.table be part of base R as they are the most popular data science packages and they are used by a large number of users?" Kind regards On Sat, Oct 5, 2019 at 4:34 PM Ant F <antoine.fabri at gmail.com> wrote: > Dear R-devel, > > The most popular piping operator sits in the package `magrittr` and is used >

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

UseRs, When doing some data manipulations using the tidyverse, I am repeatedly getting the same error message in now three separate situations. I can write up a reproducible example, but want to lay out the high-level issues in case someone recognizes exactly what is happening here. The error is: Error in mut_env_parent(overscope$.top_env, lexical_env) : object 'rlang_mut_env_parent'

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

Thanks for the feedback Jeff. Before I pursue a bug report, let me give a full example: ###### begin console output R version 3.4.1 (2017-06-30) -- "Single Candle" Copyright (C) 2017 The R Foundation for Statistical Computing Platform: i386-w64-mingw32/i386 (32-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions.

Hi Philip, You've probably realized by now that R doesn't like column names that start with a number. If you try to access an R-dataframe column named 2B or 3B with the familiar "$" notation, you'll get an error: > library(DBI) > library(RSQLite) > con2 <- dbConnect(SQLite(), "~/R_Dir/lahmansbaseballdb.sqlite") > Hack12Batting <-

This sounds an awful lot like a bug. Read the Posting Guide to know what to do about bugs. And delaying making the reprex is _always_ a bad idea. -- Sent from my phone. Please excuse my brevity. On August 14, 2017 7:26:32 AM PDT, "Szumiloski, John" <John.Szumiloski at bms.com> wrote: >UseRs, > >When doing some data manipulations using the tidyverse, I am repeatedly

> > On 7 Oct 2019, at 13:47, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > 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

This is really a feature of SQL, not R. SQL requires that you double quote column names that start with numbers, include spaces, etc., or that are SQL key words. E.g., > d <- data.frame(Order=c("sit","stay","heel"), Where=c("here","there","there"), From=c("me","me","you")) >