search for: lintr

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 calle...

...rs. It contains many things I'd like to delete: - Unused functions - Variable definitions that are never called - Unreachable code I'd write that myself, it would even be fun, but I don't want to reinvent the wheel. Is there an R package that can find these things? I've heard of lintr, but I'm not sure if it's the right tool, since, unfortunately, the code is in a folder (not a package) with many R files that are sourced from one master file and lintr can only check a single file or an actual package, from what I understand. A workaround of course would be to concate...

...to delete: > - Unused functions > - Variable definitions that are never called > - Unreachable code > > I'd write that myself, it would even be fun, but I don't want to reinvent > the wheel. > Is there an R package that can find these things? > > I've heard of lintr, but I'm not sure if it's the right tool, since, > unfortunately, the code is in a folder (not a package) with many R files > that are sourced from one master file and lintr can only check a single file > or an actual package, from what I understand. A workaround of course would &g...

...ol for better programming. I'm about to check in a new version of the task view that includes packrat and checkpoint, as they seem closer to reproducible research, but also feel like coding tools. There are a few other packages that many would find useful for better coding: devtools, testthat, lintr, codetools, svTools, rbenchmark, pkgutils, etc. This might be some overlap with the HPC task view. I would think that rJava, Rcpp and the like are better suited there but this is arguable. The last time I proposed something like this, Martin deftly convinced me to be the maintainer. It is probabl...

...2017-07-21 CRAN (R 3.4.1) jsonlite 1.5 2017-06-01 CRAN (R 3.4.0) knitr 1.17 2017-08-10 CRAN (R 3.4.1) lazyeval 0.2.0 2016-06-12 CRAN (R 3.4.0) lintr 1.0.1 2017-08-10 CRAN (R 3.4.1) magrittr 1.5 2014-11-22 CRAN (R 3.4.0) memoise 1.1.0 2017-04-21 CRAN (R 3.4.0) pkgbuild 0.0.0.9000 2017-08-31 Github (r-lib/pkgbuild a...

...gt; httr 1.3.1 2017-08-20 CRAN (R 3.4.1) > igraph 1.1.2 2017-07-21 CRAN (R 3.4.1) > jsonlite 1.5 2017-06-01 CRAN (R 3.4.0) > knitr 1.17 2017-08-10 CRAN (R 3.4.1) > lazyeval 0.2.0 2016-06-12 CRAN (R 3.4.0) > lintr 1.0.1 2017-08-10 CRAN (R 3.4.1) > magrittr 1.5 2014-11-22 CRAN (R 3.4.0) > memoise 1.1.0 2017-04-21 CRAN (R 3.4.0) > pkgbuild 0.0.0.9000 2017-08-31 Github (r-lib/pkgbuild at 6574561) > pkgconfig 2.0.1 2017-03-21 CRAN (R 3.4...

...R/oauth-token-utils.R:23 /igraph/R/lazyeval.R:219 /jsonlite/R/asJSON.data.frame.R:74 /jsonlite/R/deparse_vector.R:26 /jsonlite/R/simplifyDataFrame.R:14 /jsonlite/R/unescape_unicode.R:10 /knitr/R/utils.R:207 /knitrBootstrap/R/knit_bootstrap.R:303 /lazyeval/R/names.R:27 /learningr/R/buggy_count.R:67 /lintr/R/absolute_paths_linter.R:35 /lintr/R/absolute_paths_linter.R:71 /loo/R/helpers.R:13 /loo/R/helpers.R:20 /matconv/R/convEasySyntax.R:71 /matconv/R/convFunctionCalls.R:11 /matconv/R/utils.R:113 /micropan/R/biostrings.R:80 /micropan/R/biostrings.R:106 /mime/R/mime.R:129 /packrat/R/bundle.R:137 /packr...

...;> in a new version of the task view that includes packrat and >> checkpoint, as they seem closer to reproducible research, but also >> feel like coding tools. >> >> There are a few other packages that many would find useful for better >> coding: devtools, testthat, lintr, codetools, svTools, rbenchmark, >> pkgutils, etc. >> >> This might be some overlap with the HPC task view. I would think that >> rJava, Rcpp and the like are better suited there but this is arguable. >> >> The last time I proposed something like this, Martin def...

...that includes packrat and >>>> checkpoint, as they seem closer to reproducible research, but also >>>> feel like coding tools. >>>> >>>> There are a few other packages that many would find useful for better >>>> coding: devtools, testthat, lintr, codetools, svTools, rbenchmark, >>>> pkgutils, etc. >>>> >>>> This might be some overlap with the HPC task view. I would think that >>>> rJava, Rcpp and the like are better suited there but this is arguable. >>>> >>>> The last...

...39;m about to check > in a new version of the task view that includes packrat and > checkpoint, as they seem closer to reproducible research, but also > feel like coding tools. > > There are a few other packages that many would find useful for better > coding: devtools, testthat, lintr, codetools, svTools, rbenchmark, > pkgutils, etc. > > This might be some overlap with the HPC task view. I would think that > rJava, Rcpp and the like are better suited there but this is arguable. > > The last time I proposed something like this, Martin deftly convinced > me...

...#39;m about to check > in a new version of the task view that includes packrat and > checkpoint, as they seem closer to reproducible research, but also > feel like coding tools. > > There are a few other packages that many would find useful for better > coding: devtools, testthat, lintr, codetools, svTools, rbenchmark, > pkgutils, etc. > > This might be some overlap with the HPC task view. I would think that > rJava, Rcpp and the like are better suited there but this is arguable. > > The last time I proposed something like this, Martin deftly convinced > me to...

Hi, Both vapply() and sapply() support the 'USE.NAMES' argument. According to the man page: USE.NAMES: logical; if ?TRUE? and if ?X? is character, use ?X? as ?names? for the result unless it had names already. But if 'X' has names already and 'USE.NAMES' is FALSE, it's not clear what will happen to the names. Are they going to propagate to the result

...on of the task view that includes packrat and >>> checkpoint, as they seem closer to reproducible research, but also >>> feel like coding tools. >>> >>> There are a few other packages that many would find useful for better >>> coding: devtools, testthat, lintr, codetools, svTools, rbenchmark, >>> pkgutils, etc. >>> >>> This might be some overlap with the HPC task view. I would think that >>> rJava, Rcpp and the like are better suited there but this is arguable. >>> >>> The last time I proposed somethi...

...ighlight * R-highr * R-hms * R-htmltools * R-htmlwidgets * R-httpuv * R-httr * R-hunspell * R-igraph * R-import * R-ini * R-inline * R-IRanges * R-IRdisplay * R-IRkernel * R-iterators * R-itertools * R-jose * R-jpeg * R-jqr * R-jsonlite * R-knitr * R-labeling * R-lambda.r * R-later * R-lazyeval * R-lintr * R-listenv * R-littler * R-lmodel2 * R-lmtest * R-lokern * R-lubridate * R-maanova * R-magrittr * R-mapproj * R-maps * R-mAr * R-markdown * R-matrixStats * R-measurements * R-memoise * R-microbenchmark * R-mime * R-miniUI * R-mlbench * R-mnormt * R-mockery * R-mockr * R-msm * R-multcomp * R-multte...