Post

Quick poll: When would you like CRAN to archive your package? A: Umm, never? B: Three days before posit::conf, where you're giving a talk about said package

Oof. If you can, I'd avoid using std::regex -- I've bumped into a variety of issues over the years, and other libraries for regular expressions are typically in better shape.

Thanks Kevin, I appreciate the reply. Do you recommend any particular regex libs? For this bit of code, a simple build matters a lot (having a toml++ dep was even argued over), so maybe doing it without a regex at all would be better.

Otherwise, depending on how you're using the patterns, you could also just call grep / grepl from R (if you're on the main thread), or include PCRE2 as your own dependency if not (but make sure you compile with -fvisibility=hidden to avoid conflicts).

More or less. I can come up with more positive ways to spin it. The compounding issue here is that contacting CRAN for an exception can be hard.

The embarassing thing is that packages with a minimal test suite probably have an easier time (I suppose the ASAN issue was flagged by the package's test suite?).

Yep. CRANs policies have caused a lot of package maintainers to: 1. Remove tests 2. Remove runnable examples 3. Remove URLs in docs and references (CRAN checks URLS) It's not purely a negative thing though, it's complicated.