-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Make RustString
an extern type to avoid improper_ctypes
warnings
#132549
base: master
Are you sure you want to change the base?
Conversation
I also want to rename |
See also #116963 for general dissatisfaction with |
I'm not 100% confident that casting between normal references and extern type references like this is OK, but it seems reasonable? |
This comment has been minimized.
This comment has been minimized.
See 47e932b for why RustString is in |
a1dcb02
to
730d088
Compare
☔ The latest upstream changes (presumably #132762) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased to resolve conflicts and remove more ignore/expect added by (my) other PRs. |
#![feature(rustdoc_internals)] | ||
#![warn(unreachable_pub)] | ||
// tidy-alphabetical-end | ||
|
||
// NOTE: This crate only exists to allow linking on mingw targets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this was originally referring to, but it's pretty clearly no longer true of the present crate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it looks like a nice improvement! I just have a couple quibbles.
Addressed review feedback (diff). |
@rustbot ready |
@bors r+ |
Currently, any FFI function that uses
&RustString
needs to also add#[ignore(improper_ctypes)]
to silence a warning.The warning is not completely bogus, because
RustString
containsVec<u8>
and therefore does not have a guaranteed layout. But we have no way of telling the lint that this doesn't matter, because the C++ code only uses that pointer opaquely and never relies on its underlying layout.Ideally there would be some way to silence
improper_ctypes
at the type-definition site. But because there isn't, casting to and from a separate extern type is better than having to annotate every single use site.