Gábor Csárdi

You can create an in-place handler for the warning, that saves the stack.

You don't have to use `.Traceback` and `traceback()`, just write your own code to trap errors and copy the traceback from the worker node.

The `traceback()` output is not the best, imo. E.g. rlang's traceback trees are much better.

You can easily call C or C++ code from R, lots of packages do that. You still need to write a wrapper function that translates R objects to C/C++ objects...

In that case, you can try the RInside package.

> Using the wrong operator, like == when one should be using %in% (as per the tweet that started this) is a user error Yes. Language designers, like other people,...

> That you meant that vector recycling was a bad design idea. In which case I tend to agree. Great! Actually, recycling scalars is a good idea, recycling vectors is...

> Am I understanding top-level condition handlers correctly? Would such a TLCH (installed by {base}) be able to muffle all warnings of a certain class? In theory yes, but I...

@NelleV you might like https://github.com/r-lib/tracer#readme

rig installs R into `/opt/R`. If you installed R from your distribution, that version is completely independent of rig.