Lionel Henry
Lionel Henry
```r vectorise
```r "irteQ" %in% crancache::available_packages() #> [1] TRUE ``` This causes a revdepcheck of irteQ even though it was removed from CRAN 1 year ago.
Currently filelock restores the SIGALRM handler to its previous state but the itimer state is not restored.
In case the user env is hard to pass through. Should also make sure the direct warnings are also meaningful in the indirect case.
Means it's called interactively during development rather than from a deprecated feature. See https://github.com/tidyverse/googledrive/pull/408#discussion_r1070922708
Might be helpful for a code health report function. cc @batpigandme @mine-cetinkaya-rundel
So it can deliver information about whether call was user-facing or not.
The behaviour for soft-deprecation verbosity in unit tests was originally intented to depend on whether the soft-deprecated function is called from the tested package or downstack: - If called from...
Do we want experimental functions used from a package to throw a warning unless the package has explicitly opted in to use it? - Check that closure env of a...