On 12 August 2019 at 12:56, Wang Jiefei wrote:
| I am stuck here. I do not know if it is a bug of my package or testthat or
| the ALTREP implementation of R or possibly the interaction between them.
I don't have any concrete advice for your issue here but when I find myself
in similar debugging
Hi
I found a weird problem in testthat while working with an ALTREP package.
The package name is AltWrapper. My ALTREP serialize function is called even
when I'm trying to serialize a non-ALTREP object. Here is an example
```
context("altrep")
length_func<-function(x){
return(length(x
For reference, in the end it turned out to be caused by that "localhost"
could not be resolved. Thanks to Dominik for the report and debugging of
the problem. To be robust against such problems in the future, R now
falls back to the loopback device for localhost.
Best
Tomas
On 7/12/19 11:22 A
To throw a very small pennyworth into this debate, the metRology package I
maintain uses mixed case to highlight R for that community when I'm talking
about, or citing it. R takeup in that community is not yet high and the visible
reminder seems to help.
I'll obviously accept a consensus deci
On 8/7/19 3:10 PM, Davis Vaughan wrote:
Hi all, I'd like to ask if the following behavior is a bug. To me it
certainly feels surprising, at the very least. In this example, I would
like to call NextMethod() from my `child` object, have `cols` be left
untouched, and then substitute(cols) in the
