I happened to notice that this header file uses
#import
This is the first time I came across the preprocessor directive #import;
the first thing I found about it is this Q suggesting it's not portable
nor standard C:
https://stackoverflow.com/q/39280248/3576984
On the other hand, this exact
On 18 October 2020 at 20:56, Rafael H. M. Pereira wrote:
| The CRAN incoming Dashboard indicates that the status of my package (r5r)
| is "pending", which means 'the CRAN maintainers are waiting for an action
| on your side. You should check your emails!'.
AFAICT the text there is wrong: it
Hi all
Hi all,
I got this warning message when I run pkgdown::build_site()
Warning: Vignettes missing from index: (all the vignette names here)
And then the vignettes are not included in the package website
This didn't happen before. Does anyone know how to avoid this?
Thanks!
Marcelo
Hi all,
The CRAN incoming Dashboard indicates that the status of my package (r5r)
is "pending", which means 'the CRAN maintainers are waiting for an action
on your side. You should check your emails!'.
However, I haven't received any email with guidance on how to proceed. Is
there any CRAN
>From my side: it would be great if you (or R core) could prepare a patch, it
>would probably take me quite a bit longer than you since I don't have
>experience creating patches for R.
Best, Martin
On Sun, Oct 18, 2020, at 21:49, Gabriel Becker wrote:
> Peter et al,
>
> I had the same
Peter et al,
I had the same thought, in particular for any() and all(), which in as much
as they should work on data.frames in the first place (which to be
perfectly honest i do find quite debatable myself), should certainly work
on "logical" data.frames if they are going to work on "numeric"
Hmm, yes, this is probably wrong. E.g., we are likely to get inconsistencies
out of boundary cases like this
> a <- na.omit(airquality)
> sum(a)
[1] 37495.3
> sum(a[FALSE,])
Error in FUN(X[[i]], ...) :
only defined on a data frame with all numeric variables
Or, closer to an actual use case:
