Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: enable clippy::print_stdout and clippy::print_stderr #23732

Merged
merged 7 commits into from
May 9, 2024

Conversation

dsherret
Copy link
Member

@dsherret dsherret commented May 8, 2024

  1. Generally we should prefer to use the log crate.
  2. I very often accidentally commit eprintlns.

When we should use println or eprintln, it's not too bad to be a bit more verbose and ignore the lint rule.

@dsherret dsherret changed the title chore: enable clippy::print_stdout and clippy::prin_stderr chore: enable clippy::print_stdout and clippy::print_stderr May 8, 2024
@dsherret dsherret marked this pull request as draft May 8, 2024 02:01
@dsherret dsherret marked this pull request as ready for review May 8, 2024 15:17
@dsherret dsherret requested a review from bartlomieju May 8, 2024 16:36
@dsherret dsherret enabled auto-merge (squash) May 8, 2024 19:47
@dsherret dsherret disabled auto-merge May 8, 2024 21:49
@dsherret dsherret merged commit 47f7bed into denoland:main May 9, 2024
17 checks passed
@dsherret dsherret deleted the chore_clippy_print_stderr_stdout branch May 9, 2024 02:45
dsherret added a commit that referenced this pull request May 10, 2024
1. Generally we should prefer to use the `log` crate.
2. I very often accidentally commit `eprintln`s.

When we should use `println` or `eprintln`, it's not too bad to be a bit
more verbose and ignore the lint rule.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants