Hello:
I recently submitted a package to R using devtools:release().
I received no errors, warnings, or notes in R CMD check.
However, I received two notes in devtools::release():
1) checking CRAN incoming feasibility ... NOTE
2) checking package dependencies ... NOTE
No repository set, so c
On Sun, 1 Mar 2015, luke-tier...@uiowa.edu wrote:
On Thu, 26 Feb 2015, William Dunlap wrote:
...
It also seems to cause problems with some built-in functions:
newlapply <- function (X, FUN, ...)
{
FUN <- match.fun(FUN)
if (!is.list(X))
X <- as.list(X)
rval <- vector("list
On Thu, 26 Feb 2015, William Dunlap wrote:
...
It also seems to cause problems with some built-in functions:
newlapply <- function (X, FUN, ...)
{
FUN <- match.fun(FUN)
if (!is.list(X))
X <- as.list(X)
rval <- vector("list", length(X))
for (i in seq(along = X)) {
On Sun, 1 Mar 2015, Radford Neal wrote:
There are other instances, such as Reduce where there is a bug
report pending that amounts to the same issue. Performing surgery on
expressions and calling eval is not good practice at the R level and
probably not a good idea at the C level either. It is
> There are other instances, such as Reduce where there is a bug
> report pending that amounts to the same issue. Performing surgery on
> expressions and calling eval is not good practice at the R level and
> probably not a good idea at the C level either. It is worth thinking
> this through care
On Sun, 1 Mar 2015, Radford Neal wrote:
I think the discussion of this issue has gotten more complicated than
necessary.
The discussion has gotten no more complicated than it needs to
be. There are other instances, such as Reduce where there is a bug
report pending that amounts to the same iss
I think the discussion of this issue has gotten more complicated than
necessary.
First, there really is a bug. You can see this also by the fact that
delayed warning messages are wrong. For instance, in R-3.1.2:
> lapply(c(-1,2,-1),sqrt)
[[1]]
[1] NaN
[[2]]
[1] 1.414214
[[3]]
