cpp11 specific tweaks

Author: DavisVaughan

.claude/CLAUDE.md

@@ -6,8 +6,17 @@
 # To run code
 Rscript -e "devtools::load_all(); code"
 
-# To run all tests
-Rscript -e "devtools::test()"
+# To run R specific tests
+Rscript -e "
+  devtools::test()
+"
+
+# To run C++ specific tests
+Rscript -e "
+  devtools::install()
+  devtools::clean_dll('./cpp11test')
+  devtools::test('./cpp11test')
+"
 
 # To run all tests for files starting with {name}
 Rscript -e "devtools::test(filter = '^{name}')"
@@ -36,11 +45,11 @@ air format .
 * Always run `air format .` after generating code
 * Use the base pipe operator (`|>`) not the magrittr pipe (`%>%`)
 * Don't use `_$x` or `_$[["x"]]` since this package must work on R 4.1.
-* Use `\() ...` for single-line anonymous functions. For all other cases, use `function() {...}` 
+* Use `\() ...` for single-line anonymous functions. For all other cases, use `function() {...}`
 
 ### Testing
 
-- Tests for `R/{name}.R` go in `tests/testthat/test-{name}.R`. 
+- Tests for `R/{name}.R` go in `tests/testthat/test-{name}.R`.
 - All new code should have an accompanying test.
 - If there are existing tests, place new tests next to similar existing tests.
 - Strive to keep your tests minimal with few comments.
@@ -50,7 +59,7 @@ air format .
 - Every user-facing function should be exported and have roxygen2 documentation.
 - Wrap roxygen comments at 80 characters.
 - Internal functions should not have roxygen documentation.
-- Whenever you add a new (non-internal) documentation topic, also add the topic to `_pkgdown.yml`. 
+- Whenever you add a new (non-internal) documentation topic, also add the topic to `_pkgdown.yml`.
 - Always re-document the package after changing a roxygen2 comment.
 - Use `pkgdown::check_pkgdown()` to check that all topics are included in the reference index.
 
@@ -73,9 +82,9 @@ air format .
 
 ### Proofreading
 
-If the user asks you to proofread a file, act as an expert proofreader and editor with a deep understanding of clear, engaging, and well-structured writing. 
+If the user asks you to proofread a file, act as an expert proofreader and editor with a deep understanding of clear, engaging, and well-structured writing.
 
-Work paragraph by paragraph, always starting by making a TODO list that includes individual items for each top-level heading. 
+Work paragraph by paragraph, always starting by making a TODO list that includes individual items for each top-level heading.
 
 Fix spelling, grammar, and other minor problems without asking the user. Label any unclear, confusing, or ambiguous sentences with a FIXME comment.