Open dipterix opened 3 years ago
Yes, this is a known issue and on the road map (for way too long), e.g. Issue #62 and https://github.com/HenrikBengtsson/future.apply/issues/64#issuecomment-733487812. I just need some deep focus to get this correct; passing down envir = parent.frame()
as-is will result in some revdep complaints related to globals and ...
that need to be understood and sorted out.
Also, I was hoping to have gotten around and created https://github.com/HenrikBengtsson/future.mapreduce by now so it can just implemented it there and then future.apply, doFuture, and furrr could depend on that.
Sounds good!
In
future
, we can set environment where to search for globals, but infuture_lapply
, this option seems to be removed.Is it possible to do this:
(original code)
In this way,
future_xapply
will be able to receive environment in case other Future classes need to process the environment.https://github.com/HenrikBengtsson/future.apply/blob/fcec8077a4eb8da0b4e60dd67a20fca33715942f/R/future_xapply.R#L186-L195
We only need to change line 188 to