Replies: 1 comment
-
It is usually better to create an issue for such requests. We don't really look at the discussions page (as evident by this late response). Still happy to answer general user questions on here. But change requests for lints belong into an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The new
doc_overindented_list_items
lint makes sense in many cases. But I think it's too aggressive when it comes to argument lists. These are usually formatted in two columns, and the lint triggers if the text in the right column contains multiple lines. A real-world example from Mockall is:Another example that I found online is rust-lang/rust#57525 .
Should this lint be toned down, or is there a better way to format argument lists? In the Mockall example, the documentation is for internal use only; it isn't even generated on docs.rs. So I don't want to sacrifice readability of the source just to improve the non-existent HTML.
Beta Was this translation helpful? Give feedback.
All reactions