R's default conflict management system gives the most recently loaded package precedence. This can make it hard to detect conflicts, particularly when they arise because a package update creates ambiguity that did not previously exist. 'conflicted' takes a different approach, making every conflict an error and forcing you to choose which function to use.
Version: 1.2.0 Depends: R (≥ 3.2) Imports: cli (≥ 3.4.0), memoise, rlang (≥ 1.0.0) Suggests: callr, covr, dplyr, Matrix, methods, pkgload, testthat (≥ 3.0.0), withr Published: 2023-02-01 DOI: 10.32614/CRAN.package.conflicted Author: Hadley Wickham [aut, cre], RStudio [cph, fnd] Maintainer: Hadley Wickham <hadley at rstudio.com> BugReports: https://github.com/r-lib/conflicted/issues License: MIT + file LICENSE URL: https://conflicted.r-lib.org/, https://github.com/r-lib/conflicted NeedsCompilation: no Materials: README NEWS CRAN checks: conflicted results Documentation: Downloads: Reverse dependencies: Reverse imports: cheem, eat, rUM, tidymodels, tidyverse, usedthese, xpose.xtras Reverse suggests: boxr, destiny, DGEobj, DGEobj.utils, DOPE, duckplyr, here, marginaleffects, metaboliteIDmapping, NMRphasing, public.ctn0094data, RKaggle, roundwork, SCDB, shinyTempSignal, vegawidget, vembedr, votesmart Linking:Please use the canonical form https://CRAN.R-project.org/package=conflicted to link to this page.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4