Data Science. TileDB. Open Source. Quant Research. R. C++. Debian. Linux. Adjunct Clinical Professor, University of Illinois. Lots of coffee. And some running.
#r2u is going strongly and proving to be useful for #rstats. We had a few 80k days recently and may soon break 100k per day. Nice to see it being used!
eddelbuettel.github.io/r2u/
How it started: How it's going:
Today's edition of #ChatGPT showing us it is *clearly* not watching enough #soccer, or reading coverage in The @Guardian. "Don't know who EPL clubs CFC and FFC are." Man -- ever been to London, mate?
R^4 Post #039: Faster Feedback Systems -- A Continuous Integration Example
Comparing One Year of GitHub Action Runtimes, tiny versus tidy
dirk.eddelbuettel.com/blog/2…#rstats
Most interesting. Just how I was musing (in the quoted tweet) that (too ?) many packages still hard-wire C++11 I just noticed that one of mine now gets warnings for this on the Vienna and Oxford @debian and @fedora r-devel systems of CRAN.
#rstats#rcpp#cpp
#RStats 4.3.0 will default to C++17 (with the 'where available' caveat, just how it currently defaults to C++14). Lots of packages still specify C++11 explicitly and can just drop that (at least for builds under recent R versions).
#RStats 4.3.0 will default to C++17 (with the 'where available' caveat, just how it currently defaults to C++14). Lots of packages still specify C++11 explicitly and can just drop that (at least for builds under recent R versions).
It's the final coercion that does it: somewhat known and documented fact that the S3 class object gets dropped by #rstats. You can assemble proper (one row) data.frame objects (that you can then `rbind`), or you can avoid fate by going to character. Inject some `print` to see.