Hi all - I'm no longer here. The en-shitification of twitter under current owner is too much.
Find me elsewhere:
* mastodon: @[email protected]
* github: github.com/coolbutuseless
* blog: coolbutuseless.github.io/
#RStats #RStats4Eva
I'm really excited for the plot manipulation possibilities excalidraw opens up in #RStats !
Fantastic work by @baptnz ! nitter.gq/baptnz/status/13423417…
Current self-inflicted 'advent-of-code':
Writing an "unpack_void_ptr()" in C for interfacing #RStats with C code.
Motivating example:
A C function I need to call from R wants a 64bit unsigned integer as an argument.
How do I construct that from the R side with the least user-friction possible?
#RStats
{zstdlite} updated with latest zstd v.1.4.7
Fast, configurable in-memory compression of R objects with zstd.
* Configurable speed/compression tradeoffs
* Fast decoding
github.com/coolbutuseless/zs…
github.com/fa cebook/zstd/releases/tag/v1.4.7
#RStats
2 things I keep learning the hard way:
(1) Never get involved in a land war in asia
(2) Never try and add a finalizer to free memory that you don't own in C
#RStats
Hello segfault, my old friend....
#RStats and C go together like chalk and cheese...
#RStats experiment - directly interfacing with standard C library from R
This is actually calling the C library functions for 'fopen()' etc.
Not sure where this is going. Just pushing the boundaries to see what happens...
#RStats give mind: does anyone recall the recent work someone was doing with raw C data types in R?
It might have been using {vctrs}.
#HelpMeObiWan
I'm currently entertaining the idea of multiple C functions (all callable from R) and each one is a specific pattern of arguments to call into the variadic function with.
Definitely not scalable - but would work if I put a lot of work in...
#RStats
Google tells me there was a metal band called Emphatic who are now the current front-runners for the {emphatic} hex logo design....
#RStats
{flexo} update v0.2.1 - bug fixes!
Also added a more complicated vignette showing the beginnings of a recursive descent parser for PBRT 3d scene description format
github.com/coolbutuseless/fl…
coolbutuseless.github.io/pac…
#RStats @tylermorganwall
Introducing {flexo} - simple lex/parse tools in #RStats
I wrote {flexo} as I often need to parse structured text where no parser yet exists. {flexo} is rough but helps me prototype quickly
github.com/coolbutuseless/fl…
coolbutuseless.github.io/pac…
Note: {flexo} replaces {minilexer}
A signifier that {flexo} may be useful to you is if you have an explosion of fragile regexes in a spaghetti of ad-hoc conditional rules
#RStats
$Milion #RStats Idea(*): I wonder if you could automatically translate a limited subset of C-to-R or vice-versa
e.g. @kcf_jackson has an R-to-JS package in which he rewriting the AST
github.com/kcf-jackson/sketc…
#RStats 1/2
(*) Not a $million idea
And then automatically compile and inline the code (with {inline}).
And a heavy sprinkling of magic and get a work-a-like to "Cython" i.e. fast C implementation but only using knowledge of R
cran.r-project.org/package=i…
#RStats 2/2
Current self-inflicted advent of code: Using regex to check some user supplied regexes.
#RStats
My #RStats tombstone:
"Just need to write a quick package. Should only take a couple of hours ...."


















