Some days ago, the CRAN check with R-devel started to raise "Found non-API calls to R" NOTE. I'm not sure if they are serious on disallowing these not-so-minor APIs, but what should I do? Do you take some action or just wait? #stats
For example, rlang package now has these NOTE:
File ‘rlang/libs/rlang.so’:
Found non-API calls to R: ‘R_ClosureExpr’, ‘R_PromiseExpr’,
‘SETLENGTH’, ‘SET_ENCLOS’, ‘SET_ENVFLAGS’, ‘SET_TRUELENGTH’
@coolbutuseless@yutannihilation yeah, NOTEs won't trigger a CRAN email or any action (* until/unless they get upgraded to a warning or error), but will cause the automated checks to fail for incoming packages (sending you to human review and then probably to resubmission)
@MikeMahoney218@coolbutuseless@yutannihilation NOTEs can definitely trigger emails from CRAN, and also package archivals from CRAN, this happens all the time. (In fact CRAN might request an update even if your package check is clean.)
OTOH there is nothing to do until they do email you, sometimes they change their minds, or sometimes they only enforce new rules for new submissions.
For the case at hand my guess is that they will enforce it, and I am updating my packages. Only a guess...
For other packages it will be tougher, e.g. cpp11 uses SET_TRUELENGTH() to manage vectors with pre-allocated storage. I don't think there is a workaround there. (Well, except for nasty ones.) So every package that uses cpp11 will have that NOTE.
@gaborcsardi@MikeMahoney218@coolbutuseless I see... I don't use SET_TRUELENGTH() by myself, but have been wondering if there's any workaround. I hope there will be some alternative API.
Add comment