diff --git a/dev/articles/FAQ.html b/dev/articles/FAQ.html index d8cbca8a..86977a1c 100644 --- a/dev/articles/FAQ.html +++ b/dev/articles/FAQ.html @@ -357,10 +357,10 @@
x <- c(1L, 2L, 3L, 4L)
.Internal(inspect(x))
-#> @55a68b793528 13 INTSXP g0c2 [REF(2)] (len=4, tl=0) 1,2,3,4
+#> @56199c572e88 13 INTSXP g0c2 [REF(2)] (len=4, tl=0) 1,2,3,4
add_one(x)
.Internal(inspect(x))
-#> @55a68b793528 13 INTSXP g0c2 [REF(5)] (len=4, tl=0) 2,3,4,5
+#> @56199c572e88 13 INTSXP g0c2 [REF(5)] (len=4, tl=0) 2,3,4,5
x
#> [1] 2 3 4 5
We plan to improve on this in the future, but for now this is one of the only places where we feel it is reasonable to call diff --git a/dev/articles/cpp11.html b/dev/articles/cpp11.html index 0da386e0..3a6760cd 100644 --- a/dev/articles/cpp11.html +++ b/dev/articles/cpp11.html @@ -169,7 +169,7 @@
On my computer, it takes around 5 ms with a 1 million element
y
vector. The C++ function is about 2.5 times faster, ~2
ms, but assuming it took you 10 minutes to write the C++ function, you’d
@@ -1153,8 +1153,8 @@
Not surprisingly, our original approach with loops is very slow. Vectorising in R gives a huge speedup, and we can eke out even more performance (about ten times) with the C++ loop. I was a little diff --git a/dev/news/index.html b/dev/news/index.html index ce7464b0..d6beb89d 100644 --- a/dev/news/index.html +++ b/dev/news/index.html @@ -43,7 +43,8 @@
cpp11::writable::r_vector<T>::proxy
now implements copy assignment. Practically this means that x[i] = y[i]
now works when both x
and y
are writable vectors (#300, #339).
cpp11::function
now protects its underlying function, for maximum safety (#294).
cpp11::writable::r_vector<T>::proxy
now implements copy assignment. Practically this means that x[i] = y[i]
now works when both x
and y
are writable vectors (#300, #339).
Implicit conversion from sexp
to bool
, size_t
, and double
has been marked as deprecated and will be removed in the next version of cpp11. The 3 packages that were using this have been notified and sent PRs. The recommended approach is to instead use cpp11::as_cpp<T>
, which performs type and length checking, making it much safer to use.
New writable::data_frame
constructor that also takes the number of rows as input. This accounts for the edge case where the input list has 0 columns but you’d still like to specify a known number of rows (#272).
cpp11::writable::r_vector<T>::iterator
no longer implicitly deletes its copy assignment operator (#360).