Gábor Csárdi

> codecov.io is to code coverage as ??? is to benchmarking https://github.com/tobami/codespeed is only one I know of. You need to run your own service. Julia used to run it,...

The Julia site used to be at http://speed.julialang.org/ It is gone.

@karthik you mean internal functions? Exported functions have to be documented, otherwise `R CMD check` freaks out. But yeah, documentation coverage is not as easy to define. Documenting the internal...

`goodpractice` does not really have too much about documentation AFAIR.

@jimhester that's a good idea, but maybe some direct notification would be more appropriate, no?

> which wont make sense if a function can be easily described in a sentence or two Exactly. Small/simple functions are great, and they tend to have small manual pages.

How about using tools for readability and inconsiderate writing? E.g. http://wooorm.com/readability/ and http://alexjs.com/ These are implemented in JavaScript, but they can be ported to R easily I think.

I don't mind creating a new function, but I am not sure when this would actually happen.

Yet another way to solve this relatively painlessly is to allow calling `before_help()` and `after_help()` (and maybe `about()`) multiple times, each time possibly with a heading. The individual calls would...

> I guess the following part needs a fix similar to https://github.com/r-lib/fs/pull/280: I am not sure what you mean. `is_dir()` calls `file_info()` already, and it follows symlinks. THe problem is...