Data Science. TileDB. Open Source. Quant Research. R. C++. Debian. Linux. Adjunct Clinical Professor, University of Illinois. Lots of coffee. And some running.
Yep, indeed the fastest JSON parser by some margin.
But credit where credit is due: @knapply_ did all the juicy bits in the #Rstats package building the work by @lemire , @jkeiser2 and others after I had just put together the basic #Rcpp framework.
cloud.r-project.org/package=…
inline 0.3.17 on CRAN: Refactored, and new tests
Inline C, C++ and Fortran programs with ease in your R code
dirk.eddelbuettel.com/blog/2…
Now with much improved ability to store and reload compiled C functions thanks to @JohannesRanke#rstats
PSA: If you are working on a pull request, and not using the *magic* functionality of @magit_emacs that is `magit-checkout-pull-request` via C-g b y followed by the _pull request issue number_ then ... you are likely doing it wrong.
#rstats
"Caught you" posting and deleting a link to @Infinityssong yesterday--and but I have been binging these folks since. Their covers are pure gold. I'll check out the EP.
youtube.com/playlist?list=PL…
Recommended -- that should be good! I will miss it as I will be talking at the same time to the Cologne RUG about @Docker and the #RockerProject -- but I will be sure to check out the recording afterwards.
#rstats
Excited to be speaking about #rstats ALTREP at the @Bioconductor Developer Forum, tomorrow, Thurs Nov 19, 9AM-10AM PST. Talk will be open to the public at bluejeans.com/114067881 Come by if you're interested in learning how the guts of R work.
The screenshot shows the current version, also released into the drat repo. I cannot control CRAN admittance speed, but I can and do offer (micro)releases via the drat repo. I urge anybody working with ancient compilers to be familiar with these drat repos. Or else help test.
As does version 0.10.1.0.2, released immediately after these issues raised their head. And as stated all it takes to get a micro release from a drat repo is one added parameter : repos="RcppCore.github.io/drat". See the screenshot.
Another `tidyCpp` shoutout goes to `spdlog` by @gabi_melman: the vignette now has a demo (using `RcppSpdlog`) of the difference between "bad" (assign to `SEXP`) and "good" (instantiate) use of `Protect`. (The `spdlog` init could be common in one file, this was easy ...)
#rstats
And the new `tidyCpp` release calls for another shoutout for `minidown` by @Atsushi776 and its 'water' vignette style. Crisp yet small documents, allows for side-by-side code snippets from markdown and more, see cloud.r-project.org/web/pack… for an example.
#rstats
A refinement to yesterday's revision, correcting to 'which="most", recursive="strong"'.
As @edzerpebesma noted, the recursion makes this very expensive *very quickly*. @MattDowle proposes using only 'which="most"' which seems sensible -- see example.
#rstats
"It depends".
Per email from @MattDowle, for Rcpp it goes from 2105 to 2134 which is marginal. For another package he mentioned: from 30 to 53 which is tolerable.
There may be a hit for 'mostly Suggests' packages like test runners or vignette processors.
#rstats