Miguel Ojeda
Miguel Ojeda
### Summary `unnecessary_cast`'s does not cover some cases around `core::ffi::c_*` types that it could. ### Lint Name `unnecessary_cast` ### Reproducer I tried this code: ```rust let x = 42; let...
### Problem you are trying to solve In the Linux kernel, we would have liked to take advantage of `rustup`'s `rust-toolchain.toml` feature to simplify our Quick Start instructions (see https://github.com/Rust-for-Linux/linux/issues/953)...
Miri currently relies on Cargo and Xargo. It would be nice to support non-Cargo projects, at least via documenting the expected flags, sysroot, etc. (including bits out of `CONTRIBUTING.md` etc.).
Forward references to `enum` types end up generating the wrong type for the `enum`. For instance: ```c enum E; enum E { A }; ``` generates: ```rust pub const E_A:...
The macros that `--clang-macro-fallback` generates may conflict with the ones from e.g. an `enum`. For instance, given a header that would benefit from `--clang-macro-fallback`, such as: ```c enum { A,...
### What it does Projects typically use a single convention for safety docs and comments, typically `# Safety` sections in docs and `// SAFETY:` comments. However, it is possible for...
### Summary `unnecessary_safety_comment` appears to detect `/// SAFETY: ...` as a safety comment (i.e. not `# Safety` section) in a normal function, but it doesn't inside an `impl` block. ###...
### What it does For Rust code blocks, and for code blocks in many other languages, it is very likely that extra indentation is not indented if it is applied...
### What it does In the Linux kernel we had some documentation added with `///` instead of `//!`, which meant the docs applied to a `use` line and thus silently...
### What it does In many projects, it is likely that no indentation is not indented. Such a lint would find a few hits, e.g. there are currently a few...