> the `delayed` object is ready to be garbage collected if not assigned
immediately.
I am not sure what is meant here. Any object (at the R code level) is
ready to be garbage collected if not given a name or is not part of an
object with a name. Do you mean a 'delayed' component of a list
should
Thank you Gabriel,
Just for future readers. Below is a base R way to address this common
problem, as instructed by you (+stopifnot to suppress print).
Rscript -e 'stopifnot(file.copy("DESCRIPTION",
file.path(tdir<-tempdir(), "PACKAGES")));
db<-available.packages(paste0("file://", tdir));
install.
Sorry I think I intended to say that
1. the expressions within `delayed` don’t have to be executed if not assigned,
and
2. the enclosing runtime environment that is potentially referenced by the
objects within delayed() can be released immediately either the returned values
are referenced or