Konrad Rudolph
Konrad Rudolph
I’m now using the Nvim-R-remote configuration. When loading R and then trying to access an R documentation in Vim via `\rh`, I get this error: ``` Error detected while processing...
### Please describe your feature request Enable the following syntax: ```r box::use(stats[..., ! filter]) ``` To import and attach all names from the ‘stats’ package, except the name `filter`. This...
Currently, `box::use()` assumes that any error raised inside it must come from ‘box’ itself, and the error message/traceback is completely useless for module developers if there was an error in...
Work in progress implementation of #234. The first draft includes auto-reloading for subsequent `box::use` calls: * `box::enable_autoreload()` enables auto-reloading for `box::use` calls only. This solution should work e.g. for Shiny...
Things like * [ ] ‘roxygen2’ documentation * [ ] support for testing * [ ] support for FFI * [ ] module implementation details * [ ] imports (lack...
As discussed in #262, there should be a suite of benchmarks of different operations, and how they compare to equivalent base R operations. The results should be published as a...
Currently loading a module that isn’t already in cache parses and evaluates all its source files, which is potentially time-consuming, especially when compared to loading a package: installed R packages...
When interactively developing a script, it’s common to go back and modify, then rerun, a `box::use` top-level declaration. Currently, this causes attached environments and aliases to accumulate. To illustrate, consider...
Currently modules’ `script_path` is aware of `Rscript` and `R CMD BATCH` but not littler (except maybe incidentally). Ensure that it works.
Going forward, this package is intended to be used without being attached. It therefore can’t simply shadow the definition of `base::?` by exporting it. Instead, consider providing an appropriate `.onLoad`...