Re: [Rd] vctrs: a type system for the tidyverse

> First off, you are using the word "type" throughout this email; You seem to > mean class (judging by your Date and factor examples, and the fact you > mention S3 dispatch) as opposed to type in the sense of what is returned by > R's typeof() function. I think it would be clearer if you called it

Re: [Rd] vctrs: a type system for the tidyverse

Hadley, Looks interesting and like a fun project from what you said in the email (I don't have time right now to dig deep into the readme) A few thoughts. First off, you are using the word "type" throughout this email; You seem to mean class (judging by your Date and factor examples, and the fact

[Rd] vctrs: a type system for the tidyverse

Hi all, I wanted to share with you an experimental package that I’m currently working on: vctrs, . The motivation for vctrs is to think deeply about the output “type” of functions like `c()`, `ifelse()`, and `rbind()`, with an eye to implementing one strategy throug

[Rd] SIGSEGV in R_RunWeakRefFinalizer, object allocated with Rcpp

Hi all, I'm not sure if I'm not supposed to do the following (the dyn.unload part, I mean) or this could be a bug (in R or Rcpp): ``` Rcpp::sourceCpp(code=' #include class Object {}; //[[Rcpp::export]] SEXP new_object() { return Rcpp::XPtr(new Object()); }' ) new_object() dyn.unlo

Re: [Rd] [R] MASS::boxcox "object not found"

Hmm, this looks like a buglet/infelicity in update.lm rather than MASS::boxcox per se. Moving to R-devel. I think the story is that update.lm eventually does eval(call, parent.frame()) where the call is extracted from the lm object, but call$formula is unevaluated, and does not contain