search for: simplerror

...onsequence was a relatively large slowdown of stopifnot().. which triggered all the changes since. Whereas what we see here ["eval() inside for()"] is a cheap automatic suppression of 'call' for the "internal errors", i.e., those we don't trigger ourselves via stop(simplError(...)).

...onsequence was a relatively large slowdown of stopifnot().. which triggered all the changes since. Whereas what we see here ["eval() inside for()"] is a cheap automatic suppression of 'call' for the "internal errors", i.e., those we don't trigger ourselves via stop(simplError(...)).

...ely large slowdown of stopifnot().. which > triggered all the changes since. > > Whereas what we see here ["eval() inside for()"] is a cheap > automatic suppression of 'call' for the "internal errors", i.e., > those we don't trigger ourselves via stop(simplError(...)). > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > -- Luke Tierney Ralph E. Wareham Professor of Mathematical Sciences University of Iowa Phone: 319-335-338...

Ah, with R 3.5.0 or R 3.4.2, but not with R 3.3.1, 'eval' inside 'for' makes compiled version behave like non-compiled version. options(error = expression(NULL)) library(compiler) enableJIT(0) f <- function(x) for (i in 1) {x; eval(expression(i))} f(is.numeric(y)) # Error: object 'y' not found fc <- cmpfun(f) fc(is.numeric(y)) # Error: object 'y' not found