Dipterix Wang

@HenrikBengtsson Thanks. I think I'll write my own "promise" function then. I notice that for the new version of `future` package, `plan` will reset workers. If I my workers are...

@HenrikBengtsson Does `future` plan deprecate forked clusters in the future? I'm developing a package that requires multicore feature. PSOCK is too slow to "serialize" the data.

Hi @schloerke this is cool. How do you handle the situation where variables within the environments get changed when future is in the queue? (I'm not the maintainer, just curious)

Sorry @schloerke I wasn't making myself clear. In current implementation, `future` with `lazy=TRUE` executes immediately. If you want to have non-blocking future instances, there must be a queue for futures...

Is it possible in the function `future` specifying flag on whether this future instance will return values or not, if `yes`, `autoStopCluster` do the work, if `no`, and the cluster...

Sounds good!

Indeed, when I check shiny's default widgets, they explicitly schedule callbacks. What's weird is when I change their value via `setValue` in JS, the corresponding inputs are also changed in...

Hi @kevinushey, I encountered an error while trying to install `RcppParallel`. The package fail to compile with TBB ``` (tbb) Building TBB using bundled sources ... make[1]: Entering directory `/tmp/RtmpbCHtDl/R.INSTALL198fd18d3795c/RcppParallel/src/tbb/src'...

I see... Does that mean I have to edit the makevars instead of using configure.args?

I think you've got this email as well. ``` On 02/02/2021 08:26, > that is > > Rmpi benchmarkme bigparallelr dipsaus disk.frame runjags > > On BSD-derived OSes (principally macOS)...