AFAIK, you may use getFromNamespace to import non-exported function (e.g.
readChild <- getFromNamespace("readChild", "parallel") )
Although, I never use it myself for a package on CRANConcerning the unix only part, I don't know if it is acceptable or not, If not, maybe it could be a good idea to have a package that can install on all CRAN platform but to test OS and send a message to user whenever the functionality is not available on its OS Best, Yohann Demont On Fri, Jul 23, 2021 at 1:19 PM David Norris <da...@precisionmethods.guru> wrote: > Because parallelized progress reporting in the futureverse.org incurs > latencies too great for my application ( > https://github.com/HenrikBengtsson/progressr/issues/118), I have found it > necessary to implement my own progress reporting using some of the > non-exported functionality from `parallel`. (I do appreciate that Windows > lacks the fork() system call, and will not support this. But am willing to > make this an OS_type: unix-only package.) > > Of course, I get a WARNING for this: > > ── R CMD check results ──────────────────────────────── precautionary > 0.2.6 ──── > Duration: 6m 41.8s > > ❯ checking dependencies in R code ... WARNING > Unexported objects imported by ':::' calls: > ‘parallel:::readChild’ ‘parallel:::selectChildren’ > ‘parallel:::sendMaster’ > See the note in ?`:::` about the use of this operator. > Including base/recommended package(s): > ‘parallel’ > > Is this warning an absolute deal-killer on CRAN? Is there a 'correct' way > to do `:::` that avoids the warning altogether? > > Kind regards, > David Norris > > ______________________________________________ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
