[Rd] Plans to improve reference classes?
jmc at r-project.org
Tue Jun 23 17:11:08 CEST 2015
I understand Hadley's point; it's a consequence of the modification of the environment of the ref. class methods.
Good point, but it seems we can make that an option (there are advantages to it of code quality and ease of writing, when it works);
Let's discuss possibilities, off-list until things are a bit clearer.
On Jun 23, 2015, at 8:06 AM, Hadley Wickham <h.wickham at gmail.com> wrote:
>> 1) Is there any example or writeup on the difficulties of extending
>> reference classes across packages? Just so I can fully understand the
> Here's a simple example:
> MyRange <- setRefClass("MyRange", contains = "DiscreteRange")
> a_range <- MyRange()
> # Error in a_range$train(1:10) : could not find function "train_discrete"
> where train_discrete() is an non-exported function of the scales
> package called by the train() method of DiscreteRange.
> There are also some notes about portable vs. non-portable R6 classes
> at http://cran.r-project.org/web/packages/R6/vignettes/Portable.html
>> 2) In what sorts of situations does the performance of reference
>> classes cause problems? Sure, it's an order of magnitude slower than
>> constructing a simple environment, but those timings are in
>> microseconds, so one would need a thousand objects before it started
>> to be noticeable. Some motivating use cases would help.
> It's a bit of a pathological case, but the switch from RefClasses to
> R6 made a noticeable performance improvement in shiny. It's hard to
> quantify the impact on an app, but the impact on the underlying
> reactive implementation was quite profound: http://rpubs.com/wch/27260
> vs http://rpubs.com/wch/27264
> R6 also includes a vignette with detailed benchmarking:
> I've added Winston to the thread since he's the expert.
> R-devel at r-project.org mailing list
More information about the R-devel