Re: [R-pkg-devel] NOTE or Information?

2023-11-28 Thread Lionel Henry
I need to do an rlang release for the same format warning! I'll take this opportunity to look into conditionally exporting `%||%` from base, which should solve that warning. Best, Lionel On 11/28/23, Göran Broström wrote: > A thirty-year-old format error in the C code of my package eha was > fi

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Lionel Henry
rball to CRAN. Of course it's also fine to use the manual workflow or mix both. Best, Lionel On 4/4/23, Lionel Henry wrote: >> Here is my namespace. It says not to edit, but I had been told to add >> the importFrom. So I didn't use >> devtools::document() for fear roxygen

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Lionel Henry
an see this in the output. To solve this, add the appropriate roxygen2 tag somewhere in your package e.g. ``` #' @importFrom stats var sd etc NULL ``` Best, Lionel On 4/4/23, Lionel Henry wrote: >> Here is my namespace. It says not to edit, but I had been told to add >>

[R-pkg-devel] Frictionless alternative for `-Wstrict-prototypes`

2022-10-24 Thread Lionel Henry
Davis Vaughan and I were looking into the `-Wstrict-prototypes` warnings for C code that were recently added to the R-devel checks. We did a little research and found that these warnings are intended to catch old-style definitions and declarations that were deprecated a long time ago. This includes

Re: [R-pkg-devel] Best way to cache a dataframe available for all functions in a package

2021-11-26 Thread Lionel Henry
Hello, The trick is to store cached objects in an environment. In our team some of us have started calling this environment "the" to reflect that the elements in that environment are global singletons. Create the environment somewhere in your package: ``` the <- new.env(parent = emptyenv()) ```

Re: [R-pkg-devel] What is a "retired"package?

2021-09-21 Thread Lionel Henry
Hello, We renamed "retired" to "superseded" some time ago to avoid any confusion. Superseded functions and packages continue to be maintained on CRAN for the foreseeable future and it is safe to depend on them. See the "superseded" definition in https://tidyverse.org/lifecycle/. plyr probably sti

Re: [R-pkg-devel] Status of macOS binaries

2019-11-05 Thread Lionel Henry
> Uwe Ligges > > > On 05.11.2019 14:38, Lionel Henry wrote: > > Hello, > > > > rlang 0.4.1 was released on 24th of October, but the macOS binaries > > haven't been distributed yet. Is the binary service down? > > > > I also see the chec

[R-pkg-devel] Status of macOS binaries

2019-11-05 Thread Lionel Henry
Hello, rlang 0.4.1 was released on 24th of October, but the macOS binaries haven't been distributed yet. Is the binary service down? I also see the check results for macOS haven't been published yet, which could be related? Best, Lionel __ R-package-d