Block unreachable code and comments following return statements

Code after a top-level return() or stop() can't be reached; typically this is vestigial code left after refactoring or sandboxing code, which is fine for exploration, but shouldn't ultimately be checked in. Comments meant for posterity should be placed before the final return().

Usage

unreachable_code_linter()

See also

linters for a complete list of linters available in lintr.

Tags

best_practices, readability