You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows does not support mcapply, the multi-core parallel approach that's available on Linux and Mac. Passing an integer in as a cluster option has turned into a lot of complexity to support because it doesn't work out of the box with Windows.
We adopted pbapply because it abstracts some of the complexity of directly supporting multiple OSs, but the more I've used it, the more I've just run into problematic edge cases.
There are two directions we could take this. One, which I've implemented in testing this stuff out, is to just take on the complexity but try to get things right and well tested. The other option would be to limit what the package supports for parallelism to just limit complexity entirely. That would be to either only support parallel clusters that are pre-defined or to only support future.
I'll open a new PR with the implementation I worked up as a point of discussion.
The text was updated successfully, but these errors were encountered:
Windows does not support mcapply, the multi-core parallel approach that's available on Linux and Mac. Passing an integer in as a cluster option has turned into a lot of complexity to support because it doesn't work out of the box with Windows.
We adopted pbapply because it abstracts some of the complexity of directly supporting multiple OSs, but the more I've used it, the more I've just run into problematic edge cases.
There are two directions we could take this. One, which I've implemented in testing this stuff out, is to just take on the complexity but try to get things right and well tested. The other option would be to limit what the package supports for parallelism to just limit complexity entirely. That would be to either only support
parallel
clusters that are pre-defined or to only supportfuture
.I'll open a new PR with the implementation I worked up as a point of discussion.
The text was updated successfully, but these errors were encountered: