copy complex numbers/vectors/matrices from R to C++ and viceversa - replaces #427

Author: pachadotdev

cpp11test/man/cpp11test-package.Rd

@@ -119,6 +119,7 @@ as_tibble(x, ".rows"_nm = num_rows, ".name_repair"_nm = name_repair);
 -   Some parts of [Attributes](https://CRAN.R-project.org/package=Rcpp/vignettes/Rcpp-attributes.pdf)
     -   No dependencies
     -   No random number generator restoration
+    -   No support for roxygen2 comments
     -   No interfaces
 
 ### RNGs

man/cpp_source.Rd

@@ -349,35 +349,6 @@ For the remainder of this vignette C++ code will be presented stand-alone rather
 If you want to try compiling and/or modifying the examples you should paste them into a C++ source file that includes the elements described above.
 This is easy to do in RMarkdown by using `{cpp11}` instead of `{r}` at the beginning of your code blocks.
 
-## Roxygen support
-
-It is possible to use `roxygen2` to document your C++ functions. Here is an
-example of how to do this:
-
-```{cpp11, eval = FALSE}
-/* roxygen start
-@title Mean of a numeric vector
-@param x A numeric vector
-@return The mean of the input vector
-@examples mean_cpp(1:10)
-@export
-roxygen end */
-[[cpp11::register]]
-double mean_roxygenised_cpp(doubles x) {
-  int n = x.size();
-  double total = 0;
-  for(double value : x) {
-    total += value;
-  }
-  return total / n;
-}
-```
-
-Unlike R scripts, you need to use `/* roxygen start` and `roxygen end */` to
-delimit the roxygen comments. The logic behind this is that C++ compilers
-understand `/*` and `*/` as multi-linecomments, and therefore it is not required
-to prepend `#' ` to each line of the roxygen comments as in R scripts.
-
 ### Exercises
 
 1.  With the basics of C++ in hand, it's now a great time to practice by reading and writing some simple C++ functions. For each of the following functions, read the code and figure out what the corresponding base R function is. You might not understand every part of the code yet, but you should be able to figure out the basics of what the function does.
@@ -907,6 +878,8 @@ logicals duplicated_cpp(integers x) {
 }
 ```
 
+````{=html}
+<!--- TODO: Add `as_sexp()` support for maps
 ### Map
 
 A map is similar to a set, but instead of storing presence or absence, it can store additional data.
@@ -930,6 +903,8 @@ SEXP table_cpp(doubles x) {
   return as_sexp(counts);
 }
 ```
+!-->
+````
 
 ### Exercises
 

vignettes/converting.Rmd

@@ -332,52 +332,7 @@ Doing this universally avoids many locale specific issues when dealing with Unic
 
 Concretely cpp11 always uses `Rf_translateCharUTF8()` when obtaining `const char*` from `CHRSXP` objects and uses `Rf_mkCharCE(, CE_UTF8)` when creating new `CHRSXP` objects from `const char*` inputs.
 
-Converting R Unicode Strings to C++ Strings:
-
-```cpp
-#include <cpp11.hpp>
-#include <string>
-
-[[cpp11::register]]
-std::string convert_to_utf8(cpp11::strings input) {
-  std::string result;
-  for (auto str : input) {
-    result += cpp11::r_string(Rf_translateCharUTF8(str));
-  }
-  return result;
-}
-```
-
-```r
-# hello + how are you? in Japanese and Spanish
-input <- c("\xe3\x81\x93\xe3\x82\x93\xe3\x81\xab\xe3\x81\xa1\xe3\x81\xaf",
-  "\xc2\xbfC\xc3\xb3mo est\xc3\xa1s\x3f")
-
-convert_to_utf8(input)
-
-[1] "こんにちは¿Cómo estás?"
-```
-
-Returning Unicode Strings from C++ to R:
-
-```cpp
-#include <cpp11.hpp>
-#include <string>
-
-[[cpp11::register]]
-cpp11::writable::strings return_utf8_string() {
-  cpp11::writable::strings result;
-  std::string utf8_str = "こんにちは"; // Hello in Japanese
-  result.push_back(Rf_mkCharCE(utf8_str.c_str(), CE_UTF8));
-  return result;
-}
-```
-
-```r
-return_utf8_string()
-
-[1] "こんにちは"
-```
+<!--TODO: unicode examples?-->
 
 ## C++11 features {#c11-features}