en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Server stats:

259
active users

#rlang

0 posts0 participants0 posts today

What does #rlang need to help folks easily migrate to #codeberg ?

Some ideas:
💡codeberg equivalent to r-lib/actions
💡migration guide
💡usethis::use_codeberg() - create new repo or provide instructions for migrating if already on GitHub, similar to use_github
💡usethis::use_codeberg_ci() - equivalent to use_github_action

anything else that would help people make the jump?

Replied in thread

@embiggenData pretty much every package I write these days has little internal typed flavors of vapply. The convenience of lapply, the prescriptiveness of vapply, but without the clunkiness of having to always provide a prototype value.

vcapply (character)
vlapply (logical)
viapply (integer)

A tricked picked up when mucking around in many r-lib packages.

How many R package libraries is too many? As an experiment, I installed all my packages into separate directories - one package per library.

My .libPaths was ~400 paths long.

and… everything seems to be okay?

The purpose of this little experiment is for composing libraries dynamically, without relying on OS-specific features like symlinking.

Am I setting myself up for major performance issues or odd bugs down the road?

CRAN seems to be down… and although it’s a bit inconvenient, I’m also just amazed that this is the first time I’ve been impacted by CRAN downtime.

Maybe I’ve just been lucky so far, but upon reflection I’m pretty impressed it has a such a good uptime track record.

#r#rlang#rstats

@lionel recently introduced me to his {codegrip} package, a wonderful editor helper for reshaping function calls for RStudio & emacs.

Today I added it as a code action to {languageserver}! (currently just in a dev branch)

asciinema.org/a/QUkAj4YrK9YC4j

asciinema.org{languageserver} {codegrip} reshape as a code action!hooked up {codegrip} so that it's reshaping helpers are available in R's {languageserver} as code actions.
#r#rlang#rstats

What are your favorite R non-standard evaluation syntax “grammars”?

What do I mean a syntax grammar? I’m thinking of things like {rlang} tidy evaluation, {glue} format strings, {ggplot2} layer building, {patchwork} operators for arranging plots, {data.tables} index operator.

Some of these are more exotic syntax extensions than others, but they all provide interfaces as little grammar ecosystems.

What works well? What doesn’t? What makes a grammar have the right “feel”?

How in the hell are we still living in a universe where there is no *complete* replacement for #Mplus?

By now there should be some #rlang code, or even #Python, that takes Mplus scripts as input and just does them. And yet, no.

Everybody I know who uses Mplus says -- with complete seriousness (!!) -- that there are R packages that implement some of its functions, but they still need Mplus to do everything.

What am I missing? Why?

@rstats #wtf #science #stats #sem #structuralequationmodeling

Replied in thread

@djnavarro Sorry to be one of those people, but this is why I like #Nix for creating dev environments, all the tools can be defined alongside the project and independent of the OS and recreated exactly at any time, there's even an #RLang package that integrates R and Nix :)

b-rodrigues.github.io/rix/

b-rodrigues.github.ioRix: Reproducible Environments with NixProvides helper functions to create reproducible development environments using the Nix package manager.