Good day,
Is it possible to somehow specify more complex return types, such as a
data.frame with specific columns?
--
Dario Strbenac
University of Sydney
Camperdown NSW 2050
Australia
__
R-package-devel@r-project.org
I've sent a longish post to the R-devel mailing list with this
topic here:
https://stat.ethz.ch/pipermail/r-devel/2023-September/082892.html
In the mean time, the plan is to effectuate the change in
R-devel (the in-development version of R) on Sep.28, ~ 9:30 CEST ( =UTC+2)
Martin
___
On Tue, Sep 26, 2023 at 2:01 AM Leonard Mada via R-package-devel
wrote:
>
> Dear List-Members,
>
> There are no errors/warnings/notes when I run the check:
>
> ── R CMD check results
> Rpdb 2.3.3
> Duration: 2m 50.1s
>
> 0 errors ✔ | 0
On Tue, 26 Sep 2023, Leonard Mada via R-package-devel writes:
> Dear Members,
>
>
> How should the return values be documented, when the
> help page covers 2 related functions:
>
>
> 1.) Variant 1: fails the checks
>
> \value{
> \code{cryst1} returns a list of class \sQuote{cryst1} with the
> foll
Dear Members,
How should the return values be documented, when the help page covers 2
related functions:
1.) Variant 1: fails the checks
\value{
\code{cryst1} returns a list of class \sQuote{cryst1} with the
following components:
\describe{
\item{abc}{a numeric vector of length 3 containing
Le 26/09/2023 à 10:50, Iñaki Ucar a écrit :
On Tue, 26 Sept 2023 at 10:29, Sameh Abdulah wrote:
Thanks for replying!
The main problem that this warning from a C library that I am relying on, I
have no control to fix the warning there. So, I am still getting this warning
from R, when buildin
On Tue, 26 Sept 2023 at 10:29, Sameh Abdulah wrote:
>
> Thanks for replying!
>
> The main problem that this warning from a C library that I am relying on, I
> have no control to fix the warning there. So, I am still getting this warning
> from R, when building my package.
We don't have a way of
Thanks for replying!
The main problem that this warning from a C library that I am relying on, I
have no control to fix the warning there. So, I am still getting this warning
from R, when building my package.
Best,
--Sameh
From: R-package-devel on behalf of Jeff
Newmiller via R-package-devel
This error arises because you are not declaring the function properly before
you call it... likely because you have not included the appropriate header file
or because you have typoed the function call.
If you provide a link to your package someone may point you more precisely to
your error, bu
Thank you Ivan for all detail.
I was looking for particular algo for benchmarking purpose.
On Mon, Sep 25, 2023 at 9:26 AM Ivan Krylov wrote:
> В Sun, 24 Sep 2023 10:38:41 +0200
> Jan Gorecki пишет:
>
> >
> https://github.com/wch/r-source/blob/ed51d34ec195b89462a8531b9ef30b7b72e47204/src/main/
Dear Colleagues,
I've encountered a warning in my package that states:
'warning: a function declaration without a prototype is deprecated in all
versions of C [-Wstrict-prototypes].'
This warning originates from one of the libraries I depend on, specifically
OpenBLAS. So, I have no control to
В Tue, 26 Sep 2023 10:01:21 +0300
Leonard Mada via R-package-devel пишет:
> ── R CMD check results
Is it R CMD check or R CMD check --as-cran? You will most likely get a
NOTE when checking a package with --as-cran that had been archived on
CRAN.
> By the way: what is the purpose of this cran-c
Dear List-Members,
There are no errors/warnings/notes when I run the check:
── R CMD check results
Rpdb 2.3.3
Duration: 2m 50.1s
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
However, there is a discrepancy when I run:
usethis::use_cran_c
13 matches
Mail list logo
