-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
write_with_newline should not warn when "\n" is preceded by "\r" #4208
Comments
Hey @Geobert @matthiaskrgr! Is this issue still relevant? |
Yes it is. matthiaskrgr/rust-clippy@588dcc8 didn't fix this back then, and I think @matthiaskrgr probably forgot about this in the mean time. So feel free to take this 👍 |
Awesome! |
hi @V1shvesh are you working on this issue? If not, I have a fix. |
@metadave I haven't worked on it yet, so feel free! Thanks! |
PR has been integrated, I'm closing this. :) |
No, it's |
don't warn on CRLF in `with_newline` lints changelog: don't warn on CRLF in `print_with_newline` and `write_with_newline` fixes rust-lang#4208. This PR also transitions the unescaping logic to use the compiler's lexer.
don't warn on CRLF in `with_newline` lints changelog: don't warn on CRLF in `print_with_newline` and `write_with_newline` fixes rust-lang#4208. This PR also transitions the unescaping logic to use the compiler's lexer.
don't warn on CRLF in `with_newline` lints changelog: don't warn on CRLF in `print_with_newline` and `write_with_newline` fixes #4208. This PR also transitions the unescaping logic to use the compiler's lexer.
don't warn on CRLF in `with_newline` lints changelog: don't warn on CRLF in `print_with_newline` and `write_with_newline` fixes #4208. This PR also transitions the unescaping logic to use the compiler's lexer.
don't warn on CRLF in `with_newline` lints changelog: don't warn on CRLF in `print_with_newline` and `write_with_newline` fixes #4208. This PR also transitions the unescaping logic to use the compiler's lexer.
Writing to a file, I need CRLF format so I have no other choice than using
write
with\r\n
.The text was updated successfully, but these errors were encountered: