Create safe LLVM bindings #8274
Labels
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
Comments
|
Visiting for triage. Still an issue. I'm not convinced we should continue using their C API, but it's incredibly inconvenient to have to wrap the C++ one manually. Their C++ API is slowly evolving under the C API, and the C API is frozen. |
|
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#644 |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jan 17, 2022
Update markdown-it version Fixes improperly-escaped pipes in Markdown tables for the [documentation of bad_bit_mask](https://rust-lang.github.io/rust-clippy/master/index.html#bad_bit_mask) and [ineffective_bit_mask](https://rust-lang.github.io/rust-clippy/master/index.html#ineffective_bit_mask). A column pipe takes precedence over inline code markers, so some back ticks are displayed literally and the pipes need to be escaped. I found no other occurrences of the same problem when searching rust-clippy by ```\|.*`.*\|```. changelog: Update markdown-it version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rustc's LLVM bindings are a bit of a hodgepodge. Some abstractions have been added on top of the C bindings, but not consistently. It would be nice to do some serious cleanup here so that rustc is using only safe, high-level bindings.
The text was updated successfully, but these errors were encountered: