Skip to content

tabs_in_doc_comments suggests me to use spaces for indentation #7309

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

Open
piegamesde opened this issue Jun 2, 2021 · 0 comments
Open

tabs_in_doc_comments suggests me to use spaces for indentation #7309

piegamesde opened this issue Jun 2, 2021 · 0 comments
Labels
C-bug Category: Clippy is not doing the correct thing I-false-positive Issue: The lint was triggered on code it shouldn't have

Comments

@piegamesde
Copy link

Lint name: tabs_in_doc_comments

I tried this code:

	/**
	 * Some code documentation
	 * string.
	 */

I expected to see this happen: The lint only activates when using tabs within the comment block, and not to indent the block.

Instead, this happened: I get a lint suggesting to replace my tabs with spaces. Doing this would result in mixed indentation (I generally use tabs and the lines with the comment would use spaces instead), which is bad.

Meta

  • cargo clippy -V: clippy 0.1.51 (2fd73fa 2021-03-23)
  • rustc -Vv:
    rustc 1.51.0 (2fd73fabe 2021-03-23)
    binary: rustc
    commit-hash: 2fd73fabe469357a12c2c974c140f67e7cdd76d0
    commit-date: 2021-03-23
    host: x86_64-unknown-linux-gnu
    release: 1.51.0
    LLVM version: 11.0.1
    
@piegamesde piegamesde added C-bug Category: Clippy is not doing the correct thing I-false-positive Issue: The lint was triggered on code it shouldn't have labels Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Clippy is not doing the correct thing I-false-positive Issue: The lint was triggered on code it shouldn't have
Projects
None yet
Development

No branches or pull requests

1 participant