Displaying 9 results from an estimated 9 matches for "usethis".
2018 Aug 23
7
conflicted: an alternative conflict resolution strategy
...er`: dplyr, stats
#> * `lag` : dplyr, stats
- Deprecated functions should never win a conflict, so conflicted
checks for use of `.Deprecated()`. This rule is very useful when
moving functions from one package to another. For example, many
devtools functions were moved to usethis, and conflicted ensures
that you always get the non-deprecated version, regardess of package
attach order:
head(conflict_scout(c("devtools", "usethis")))
#> 26 conflicts:
#> * `use_appveyor` : [usethis]
#> * `use_build_igno...
2018 Aug 24
1
conflicted: an alternative conflict resolution strategy
...ter`: dplyr, stats
#> * `lag` : dplyr, stats
- Deprecated functions should never win a conflict, so conflicted
checks for use of `.Deprecated()`. This rule is very useful when
moving functions from one package to another. For example, many
devtools functions were moved to usethis, and conflicted ensures
that you always get the non-deprecated version, regardess of package
attach order:
head(conflict_scout(c("devtools", "usethis")))
#> 26 conflicts:
#> * `use_appveyor` : [usethis]
#> * `use_build_ignor...
2018 Aug 24
0
conflicted: an alternative conflict resolution strategy
...#> * `lag` : dplyr, stats
>
> - Deprecated functions should never win a conflict, so conflicted
> checks for use of `.Deprecated()`. This rule is very useful when
> moving functions from one package to another. For example, many
> devtools functions were moved to usethis, and conflicted ensures
> that you always get the non-deprecated version, regardess of package
> attach order:
>
> head(conflict_scout(c("devtools", "usethis")))
> #> 26 conflicts:
> #> * `use_appveyor` : [usethis]
&g...
2018 Aug 23
0
conflicted: an alternative conflict resolution strategy
...gt; * `lag` : dplyr, stats
>
> - Deprecated functions should never win a conflict, so conflicted
> checks for use of `.Deprecated()`. This rule is very useful when
> moving functions from one package to another. For example, many
> devtools functions were moved to usethis, and conflicted ensures
> that you always get the non-deprecated version, regardess of package
> attach order:
>
> head(conflict_scout(c("devtools", "usethis")))
> #> 26 conflicts:
> #> * `use_appveyor` : [useth...
2017 Sep 06
3
withr::set_makevars
...7-08-31 Github (rstudio/rstudioapi at e1e466b)
sessioninfo 1.0.1 2017-08-31 Github (r-lib/sessioninfo at e813de4)
stringi 1.1.5 2017-04-07 CRAN (R 3.4.0)
stringr 1.2.0 2017-02-18 CRAN (R 3.4.0)
usethis 0.0.0.9000 2017-08-31 Github (r-lib/usethis at 12e6f95)
whoami 1.1.1 2015-07-13 CRAN (R 3.4.0)
withr 2.0.0 2017-07-28 CRAN (R 3.4.1)
xml2 1.1.1 2017-01-24 CRAN (R 3.4.0)...
2017 Sep 07
0
withr::set_makevars
...(R 3.4.0)
> rstudioapi 0.6.0.9000 2017-08-31 Github (rstudio/rstudioapi at e1e466b)
> sessioninfo 1.0.1 2017-08-31 Github (r-lib/sessioninfo at e813de4)
> stringi 1.1.5 2017-04-07 CRAN (R 3.4.0)
> stringr 1.2.0 2017-02-18 CRAN (R 3.4.0)
> usethis 0.0.0.9000 2017-08-31 Github (r-lib/usethis at 12e6f95)
> whoami 1.1.1 2015-07-13 CRAN (R 3.4.0)
> withr 2.0.0 2017-07-28 CRAN (R 3.4.1)
> xml2 1.1.1 2017-01-24 CRAN (R 3.4.0)
> xmlparsedata 1.0.1 2016-06-18 CRAN (R 3.4.0)...
2018 Aug 24
0
conflicted: an alternative conflict resolution strategy
...#> * `lag` : dplyr, stats
>
> - Deprecated functions should never win a conflict, so conflicted
> checks for use of `.Deprecated()`. This rule is very useful when
> moving functions from one package to another. For example, many
> devtools functions were moved to usethis, and conflicted ensures
> that you always get the non-deprecated version, regardess of package
> attach order:
>
I would completely believe this rule is useful for refactoring as you
describe, but that is the "same function" case. For an end-user in the
"different f...
2019 Jul 04
2
Fwd: Fedora 31 System-Wide change proposal: Automatic R runtime dependencies
...ler
* R-SummarizedExperiment
* R-svglite
* R-sys
* R-sysfonts
* R-systemfit
* R-testit
* R-testthat
* R-tibble
* R-tidyr
* R-tidyselect
* R-tikzDevice
* R-timeDate
* R-timeSeries
* R-tinytest
* R-tinytex
* R-tkrplot
* R-tkWidgets
* R-tufte
* R-tweenr
* R-udunits2
* R-unitizer
* R-units
* R-unix
* R-usethis
* R-utf8
* R-uuid
* R-V8
* R-vctrs
* R-viridisLite
* R-waveslim
* R-wavethresh
* R-webp
* R-webutils
* R-whisker
* R-whoami
* R-widgetTools
* R-withr
* R-xfun
* R-XML
* R-xml2
* R-xopen
* R-xtable
* R-XVector
* R-yaml
* R-zeallot
* R-zoo
* libsbml
* libsedml
* libnuml
* shogun
== Contingency Plan...
2019 Oct 05
4
should base R have a piping operator ?
Hi John,
Thanks, but the Bizzaro pipe comes with many flaws though :
* It's not a single operator
* It has a different precedence
* It cannot be used in a subcall
* The variable assigned to must be on the right
* It doesn't trigger indentation when going to the line
* It creates/overwrite a `.` variable in the worksace.
And it doesn't deal gracefully with some lazy evaluation edge