Kirill Müller

Sure, one could make scripts safer against undesired auto-recycling with a TLCH. Another use case is evaluation of expressions supplied as user input -- in this case it seems that...

I suspect that memuse doesn't report peak memory accurately. On Linux, I see with an Excel file of 1 MB (!!!): ``` $ R -q -e 'invisible(unix::rlimit_as(210e6)); readxl::read_xlsx' # out...

I'm aware of the version-specific executables. I'd expect `rim run` to define `$PATH` in a way that ensures that `R` and perhaps other important executables point to the selected versions....

I'm working on (finally!) releasing utf8, this means we could release styler soon. After this I think we could start thinking about that 80-character rule, because editing code from "wide"...

No, that would be after styling, when we know the final width -- we'd just add linebreaks but not change much otherwise.

I remember Hadley suggested that an empty line after a long function header helps readability. I wouldn't formalize this as a rule yet, but I've seen this pattern a few...

I have tweaked the "bad" example in the original post. Keeping an extra newline, at least in non-strict mode, doesn't sound too bad as a starter.

Rewriting the history for a repository needs fast styling of repetitive inputs. I don't mind if this lives in a branch for now. Maybe we can make it opt-in?

@coala: The _styler_ package is a new way of formatting R code, would you be interested to integrate it?

I guess so, but perhaps we need to argue with the maintainers why this is safe to do. There's also https://prettier.io/ which doesn't seem to have an R plugin yet.