CLEANUP: Remove need for calling resolved(future, run = FALSE)

Author: HenrikBengtsson

DESCRIPTION

@@ -1,5 +1,5 @@
 Package: future
-Version: 1.68.0-9028
+Version: 1.68.0-9029
 Title: Unified Parallel and Distributed Processing in R for Everyone
 Depends:
     R (>= 3.2.0)

R/backend_api-03.MultiprocessFutureBackend-class.R

@@ -60,7 +60,14 @@ listFutures.MultiprocessFutureBackend <- function(backend, ..., debug = FALSE) {
       counter <- as.integer(future[["uuid"]][2])
       start <- future[["start"]]
       if (is.null(start)) start <- NA_real_ ## happens if future is reset
-      resolved <- resolved(future, run = FALSE)
+
+      ## Avoid triggering resolved() launching a lazy future
+      if (future[["state"]] == "created") {
+        resolved <- FALSE
+      } else {
+        resolved <- resolved(future)
+      }
+      
       data.frame(
         counter = counter,
         start = start,

R/backend_api-FutureRegistry.R

@@ -87,7 +87,8 @@ FutureRegistry <- local({
       ## NOTE: It is when calling resolved() on a future with
       ##       early signaling is enabled that conditioned
       ##       may be signaled.
-      if (resolved(future, run = FALSE, .signalEarly = FALSE)) {
+      if ((!future[["state"]] %in% "created") &&
+          resolved(future, .signalEarly = FALSE)) {
         if (debug) mdebugf_push("Future at position #%d is resolved ...", ii)
         ## (a) Let future cleanup after itself, iff needed.
         ##     This, this may result in a call to