Replies: 2 comments 1 reply
-
We are usually careful with suggesting external crates, as we don't want to put the impression, that we favor one crate over another. For logging: Why suggest So I wouldn't put this in the lint suggestion, but we could include this information in the lint documentation and either link the awesome-rust page EDIT: Just saw that the last commit to the cookbook was 3 years ago, so maybe not that |
Beta Was this translation helpful? Give feedback.
-
As I now seem to understand there is some explanation that comes with clippy and is printed on the terminal and there is more information on the web site that clippy refers to. I need to understand the separation between the two, but I was thinking about the web site. Maybe the link should be to the logging crates as mentioned above or to to the logging tag on crates.io So:
|
Beta Was this translation helpful? Give feedback.
-
Once in a while I feel that the explanations of the lints could include more suggestions. e.g print_stdout could include the suggestion to replace the debugging print statement with
log::debug!
Something like this:
I'd be happy to send such extensions whenever encounter something, assuming the general concept of giving more detailed suggestion is something that is seen as positive.
Beta Was this translation helpful? Give feedback.
All reactions