Currently, future exports quite a few functions beyond the Future API itself. Some of them are used by backends but not really needed by uses of future per se - can they be removed from the public API?
For example, future.callr use MultiprocessFuture, which belongs more to a "protected" backend API. Maybe there's a robust way to make those available without exporting them, e.g.
MultiprocessFuture <- future::import_protected("MultiprocessFuture")OTH, with such an approach we'll lose all the advantages that come with R CMD check, e.g. code inspection. Maybe that's ok.
Currently, future exports quite a few functions beyond the Future API itself. Some of them are used by backends but not really needed by uses of future per se - can they be removed from the public API?
For example, future.callr use
MultiprocessFuture, which belongs more to a "protected" backend API. Maybe there's a robust way to make those available without exporting them, e.g.OTH, with such an approach we'll lose all the advantages that come with
R CMD check, e.g. code inspection. Maybe that's ok.