lintr: A 'Linter' for R Code

title: "Static Code Analysis for R" date: "2025-04-01" tags: ["R", "linter", "tidyverse"] authors: - name: Jim Hester affiliation: 1 orcid: 0000-0002-2739-7082 - name: Florent Angly affiliation: 2 orcid: 0000-0002-8999-0738 - name: Michael Chirico affiliation: 3 orcid: 0000-0003-0787-087X - name: Russ Hyde affiliation: 4 orcid: ~ - name: Ren Kun affiliation: 5 orcid: ~ - name: Indrajeet Patil orcid: 0000-0003-1995-6531 affiliation: 6 - name: Alexander Rosenstock affiliation: 7 orcid: ~ affiliations: - index: 1 name: Netflix - index: 2 name: The University of Queensland - index: 3 name: Google - index: 4 name: Jumping Rivers - index: 5 name: Unknown - index: 6 name: Carl Zeiss AG, Germany - index: 7 name: Mathematisches Institut der Heinrich-Heine-Universität Düsseldorf output: md_document: variant: "markdown" preserve_yaml: true standalone: true bibliography: paper.bib csl: apa.csl link-citations: true

Statement of Need

In computer programming, "linting" is the process of analyzing the source code to identify possible programming and stylistic problems [@enwiki:1260589258] and a linter is a tool used for linting. A linter analyzes code to identify potential errors, stylistic issues, or deviations from coding standards. It helps ensure consistency, readability, and best practices by flagging common mistakes, such as syntax errors, unused variables, or improper formatting. Linters are essential for improving code quality, preventing bugs, and maintaining a clean codebase, especially in collaborative development environments [@enwiki:1218663830]. {lintr} is an open-source package that provides linters for the R programming language, which is an interpreted, dynamically-typed programming language [@base2023], and is used by a wide range of researchers and data scientists. {lintr} can thus act as a valuable tool for R users to help improve the quality and reliability of their code.

Features

By default, {lintr} enforces the tidyverse style guide [@Wickham2023,@Müller2024]. In this respect, it differs from other static code analysis tools in R (like {codetools} [@Tierney2024]), which are not opinionated and don't enforce any particular style of writing code, but, rather, check R code for possible problems (incidentally, {lintr} uses {codetools} as a backend for object usage linters). Additionally, {lintr} is concerned only with R code, so code-adjacent text like inline {roxygen2} comments [@Wickham2024roxy] will not be covered (cf. {roxylint} [@Kelkhoff2024]).

As of this writing, {lintr} offers 113 linters.

library(lintr)

length(all_linters())
#> [1] 113

Naturally, we can't discuss all of them here. To see the most up-to-date details about all the available linters, we encourage readers to visit https://lintr.r-lib.org/dev/reference/index.html#individual-linters.

We will showcase one linter for each kind of common problem found in R code.

Best practices

{lintr} offers linters that can detect problematic antipatterns and suggest alternatives that follow best practices.

For example, expressions like ifelse(x, TRUE, FALSE) and ifelse(x, FALSE, TRUE) are redundant; just x or !x suffice in R code where logical vectors are a core data structure. The redundant_ifelse_linter() linter detects such discouraged usages.

lint(
  text = "ifelse(x >= 2.5, TRUE, FALSE)",
  linters = redundant_ifelse_linter()
)
#> <text>:1:1: warning: [redundant_ifelse_linter] Just use the
#>     logical condition (or its negation) directly instead of
#>     calling ifelse(x, TRUE, FALSE)
#> ifelse(x >= 2.5, TRUE, FALSE)
#> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~

lint(
  text = "x >= 2.5",
  linters = redundant_ifelse_linter()
)
#> i No lints found.

Efficiency

Sometimes users might not be aware of a more efficient way offered by R for carrying out a computation. {lintr} offers linters to improve code efficiency by avoiding common inefficient patterns.

For example, the any_is_na_linter() linter detects usages of any(is.na(x)) and suggests anyNA(x) as a more efficient alternative to detect presence of any missing values.

lint(
  text = "any(is.na(x), na.rm = TRUE)",
  linters = any_is_na_linter()
)
#> <text>:1:1: warning: [any_is_na_linter] anyNA(x) is better
#>     than any(is.na(x)).
#> any(is.na(x), na.rm = TRUE)
#> ^~~~~~~~~~~~~~~~~~~~~~~~~~~

anyNA() in R is more efficient than any(is.na()) because it stops execution once a missing value is found, while is.na() evaluates the entire vector.

lint(
  text = "anyNA(x)",
  linters = any_is_na_linter()
)
#> i No lints found.

Readability

Coders spend significantly more time reading than writing code [@mcconnell2004code]. Thus, writing readable code makes the code more maintainable and reduces the possibility of introducing bugs stemming from a poor understanding of the code.

{lintr} provides a number of linters that suggest more readable alternatives. For example, comparison_negation_linter() blocks usages like !(x == y) where a direct relational operator is appropriate.

lint(
  text = "!x == 2",
  linters = comparison_negation_linter()
)
#> <text>:1:1: warning: [comparison_negation_linter] Use x !=
#>     y, not !(x == y).
#> !x == 2
#> ^~~~~~~

Note also the complicated operator precedence. The more readable alternative here uses !=:

lint(
  text = "x != 2",
  linters = comparison_negation_linter()
)
#> i No lints found.

Tidyverse style

{lintr} also provides linters to enforce the style used throughout the {tidyverse} [@Wickham2019] ecosystem of R packages. This style of coding has been outlined in the tidyverse style guide [@Wickham2023].

For example, the style guide recommends using snake_case for identifiers:

lint(
  text = "MyVar <- 1L",
  linters = object_name_linter()
)
#> <text>:1:1: style: [object_name_linter] Variable and
#>     function name style should match snake_case or symbols.
#> MyVar <- 1L
#> ^~~~~

lint(
  text = "my_var <- 1L",
  linters = object_name_linter()
)
#> i No lints found.

Common mistakes

One category of linters helps you detect some common mistakes statically and provide early feedback.

For example, duplicate arguments in function calls can sometimes cause run-time errors:

mean(x = 1:5, x = 2:3)
#> Error in mean(x = 1:5, x = 2:3): formal argument "x" matched by multiple actual arguments

But duplicate_argument_linter() can check for this statically:

lint(
  text = "mean(x = 1:5, x = 2:3)",
  linters = duplicate_argument_linter()
)
#> <text>:1:15: warning: [duplicate_argument_linter] Avoid
#>     duplicate arguments in function calls.
#> mean(x = 1:5, x = 2:3)
#>               ^

Even for cases where duplicate arguments are not an error, this linter explicitly discourages duplicate arguments.

lint(
  text = "list(x = TRUE, x = FALSE)",
  linters = duplicate_argument_linter()
)
#> <text>:1:16: warning: [duplicate_argument_linter] Avoid
#>     duplicate arguments in function calls.
#> list(x = TRUE, x = FALSE)
#>                ^

This is because objects with duplicated names objects can be hard to work with programmatically and should typically be avoided.

l <- list(x = TRUE, x = FALSE)
l["x"]
#> $x
#> [1] TRUE
l[names(l) == "x"]
#> $x
#> [1] TRUE
#> 
#> $x
#> [1] FALSE

Extensibility

{lintr} is designed for extensibility by allowing users to easily create custom linting rules. There are two main ways to customize it:

Use additional arguments in existing linters. For example, although tidyverse style guide prefers snake_case for identifiers, if a project's conventions require it, the relevant linter can be customized to support it:

lint(
  text = "my.var <- 1L",
  linters = object_name_linter(styles = "dotted.case")
)
#> i No lints found.

Create new linters (by leveraging functions like lintr::make_linter_from_xpath()) tailored to match project- or organization-specific coding standards.

Indeed, {goodpractice} [@Padgham2024] bundles a set of custom linters that are not part of the default set of {lintr} linters, while {box.linters} [@Basa2024] extends {lintr} to support {box} modules [@Rudolph2024] and {checklist} includes linters as one of the strict checks for R packages [@Onkelinx2024]. {flir} [@Bacher2024] is a Rust-backed analogue inspired by {lintr} that also provides support for fixing lints.

Benefits of using `{lintr}`

There are several benefits to using {lintr} to analyze and improve R code. One of the most obvious is that it can help users identify and fix problems in their code, which can save time and effort during the development process. By catching issues early on, {lintr} can help prevent bugs and other issues from creeping into code, which can save time and effort when it comes to debugging and testing.

Another benefit of {lintr} is that it can help users write more readable and maintainable code. By enforcing a consistent style and highlighting potential issues, {lintr} can help users write code that is easier to understand and work with. This is especially important for larger projects or teams, where multiple contributors may be working on the same codebase and it is important to ensure that code is easy to follow and understand, particularly when frequently switching context among code primarily authored by different people. {lintr} is designed to be easy to use and integrate into existing workflows, and can be used as part of an automated build or continuous integration process. {lintr} also integrates with a number of popular IDEs and text editors, such as RStudio and Visual Studio Code, making it convenient for users to run {lintr} checks on their code as they work.

It can also be a useful tool for teaching and learning R. By providing feedback on code style and potential issues, it can help users learn good coding practices and improve their skills over time. This can be especially useful for beginners, who may not yet be familiar with all of the best practices for writing R code.

Finally, {lintr} has had a large and active user community since its birth in 2014 which has contributed to its rapid development, maintenance, and adoption. At the time of writing, {lintr} is in a mature and stable state and therefore provides a reliable API that is unlikely to feature fundamental breaking changes.

Conclusion

{lintr} is a valuable tool for R users to help improve the quality and reliability of their code. Its static code analysis capabilities, combined with its flexibility and ease of use, make it relevant and valuable for a wide range of applications.

Licensing and Availability

{lintr} is licensed under the MIT License, with all source code openly developed and stored on GitHub (https://github.com/r-lib/lintr), along with a corresponding issue tracker for bug reporting and feature enhancements.

Conflicts of interest

The authors declare no conflict of interest.

Funding

This work was not financially supported by any of the affiliated institutions of the authors.

Acknowledgments

{lintr} would not be possible without the immense work of the R-core team who maintain the R language and we are deeply indebted to them. We are also grateful to all contributors to {lintr}.