Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMore thorough use of storage policy in Vector internals #850
Conversation
|
I see this failing on Travis. At least this test has an issue:
Can you take another look? |
|
Looks like a name attribute may not get dropped ? R> library(Rcpp)
R> sourceCpp("~/git/rcpp/inst/unitTests/cpp/DataFrame.cpp")
R> DF <- data.frame(a=1:3, b=c("a","b","c"), stringsAsFactors = FALSE )
R> RUnit::checkEquals( createTwoStringsAsFactors(), DF, msg = "DataFrame create2 stringsAsFactors = false")
Error in RUnit::checkEquals(createTwoStringsAsFactors(), DF, msg = "DataFrame create2 stringsAsFactors = false") :
Names: 2 string mismatches
DataFrame create2 stringsAsFactors = false
R> DF
a b
1 1 a
2 2 b
3 3 c
R> createTwoStringsAsFactors()
X1.3 c..a....b....c..
1 1 a
2 2 b
3 3 c
R> |
|
should be better now. |
|
Yes, indeed -- thanks. I happened to have run reverse depends on a machine this week, so I turned on a new one. We'll know in a few hours if that shows something unexpected. |
|
No issues, so merging. |
|
Great thanks. I’ll probably find out more of these if I start using alternative storage policies. |
|
BTW I have had See eg here for a summary. I have logs if you need them. |
|
A new version has been sent to cran, two weeks ago. |
|
Right. I even knew that. RcppArmadillo sat in the same 'inspect' corner for over a week too. |
This was a but more than I anticipated. Probably not exhaustive. but it makes the tests pass.