Closed HenrikBengtsson closed 8 years ago
UPDATE: Plan is now to make BatchJobsFuture self-contained, cf. Issue #51. After this, then asyncBatchEvalQ()
could relying on BatchJobsFuture instead, or more likely, be completely dropped.
Decided to drop asyncBatchEvalQ()
, because it's not part of the basic future API.
Update
asyncBatchEvalQ()
to handle globals just like future package. Export that functionality in the future package to be used by async?