Lint common mistakes/style issues cropping up from return statements

return(x <- ...) is either distracting (because x is ignored), or confusing (because assigning to x has some side effect that is muddled by the dual-purpose expression).

Usage

function_return_linter()

See also

linters for a complete list of linters available in lintr.

Tags

best_practices, readability

Examples

# will produce lints
lint(
  text = "foo <- function(x) return(y <- x + 1)",
  linters = function_return_linter()
)
#> ::warning file=<text>,line=1,col=27::file=<text>,line=1,col=27,[function_return_linter] Move the assignment outside of the return() clause, or skip assignment altogether.

lint(
  text = "foo <- function(x) return(x <<- x + 1)",
  linters = function_return_linter()
)
#> ::warning file=<text>,line=1,col=27::file=<text>,line=1,col=27,[function_return_linter] Move the assignment outside of the return() clause, or skip assignment altogether.

writeLines("e <- new.env() \nfoo <- function(x) return(e$val <- x + 1)")
#> e <- new.env() 
#> foo <- function(x) return(e$val <- x + 1)
lint(
  text = "e <- new.env() \nfoo <- function(x) return(e$val <- x + 1)",
  linters = function_return_linter()
)
#> ::warning file=<text>,line=2,col=27::file=<text>,line=2,col=27,[function_return_linter] Move the assignment outside of the return() clause, or skip assignment altogether.

# okay
lint(
  text = "foo <- function(x) return(x + 1)",
  linters = function_return_linter()
)

code_lines <- "
foo <- function(x) {
  x <<- x + 1
  return(x)
}
"
lint(
  text = code_lines,
  linters = function_return_linter()
)

code_lines <- "
e <- new.env()
foo <- function(x) {
  e$val <- x + 1
  return(e$val)
}
"
writeLines(code_lines)
#> 
#> e <- new.env()
#> foo <- function(x) {
#>   e$val <- x + 1
#>   return(e$val)
#> }
#> 
lint(
  text = code_lines,
  linters = function_return_linter()
)