We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried this code:
#![allow(text_direction_codepoint_in_comment)]
I expected to see this happen: text_direction_codepoint_in_comment to be allowed
text_direction_codepoint_in_comment
Instead, this happened:
warning: unknown lint: `text_direction_codepoint_in_comment` --> src/main.rs:1:10 | 1 | #![allow(text_direction_codepoint_in_comment)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: did you mean: `text_direction_codepoint_in_literal` | = note: `#[warn(unknown_lints)]` on by default
(in case anyone is curious why I noticed this, don't worry, this isn't due to production code, see https://codegolf.stackexchange.com/a/230964/3103)
rustc --version --verbose:
rustc --version --verbose
rustc 1.56.1 (59eed8a2a 2021-11-01) binary: rustc commit-hash: 59eed8a2aac0230a8b53e89d4e99d55912ba6b35 commit-date: 2021-11-01 host: x86_64-unknown-linux-gnu release: 1.56.1 LLVM version: 13.0.0
The text was updated successfully, but these errors were encountered:
cc @estebank
Sorry, something went wrong.
@rustbot claim
f5f6f73
That will show me not add proper test coverage 🤦♀️
hkratz
Successfully merging a pull request may close this issue.
I tried this code:
#![allow(text_direction_codepoint_in_comment)]
I expected to see this happen:
text_direction_codepoint_in_comment
to be allowedInstead, this happened:
(in case anyone is curious why I noticed this, don't worry, this isn't due to production code, see https://codegolf.stackexchange.com/a/230964/3103)
Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: