-
Notifications
You must be signed in to change notification settings - Fork 13.3k
"ctypes" lint name is confusing #14704
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
Comments
|
Aren't they literally "types from C", or "C-compatible data types"? I think it's an analogy to the ctypes Python module. |
@nathantypanski yes, but the problem is not with the meaning of "ctypes" but with the pairing of "allow" and "ctypes". When you read the words "allow ctypes" you intuitively think, "by typing these words I am allowed to use C types", but that is not what |
So would one just need to change every occurrence of CTYPES in src/librustc/lint/builtin.rs to FFI_RUST_TYPES? |
This is now called improper_ctypes. |
Fix some mir related bugs fix rust-lang#14701 fix rust-lang#14704
Fix evaluating negative for floating point types fix rust-lang#14704 Unary operators was missed from rust-lang#14705
I just wrote
#[allow(ctypes)]
which means "allow non-c types".The text was updated successfully, but these errors were encountered: