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
unsafe extern "C"
The babble Rust plugin should emit unsafe extern "C" blocks instead of just extern "C".
babble
extern "C"
See RFC 3484.
A specific error when running cargo fix --edition on a Rust 2021 babble project looks like this:
cargo fix --edition
warning: extern blocks should be unsafe --> /home/moritz/code/crates/bbl-oiio/target/debug/build/openimageio-98c7a6140b96515b/out/build/oiio.rs:339:1 | 339 | extern "C" { | ^ | | | _help: needs `unsafe` before the extern keyword: `unsafe` | | 340 | | 341 | | pub fn oiio_CspanF32_ctor(data: *mut c_float, size: c_ulong, _result: *mut *mut oiio_CspanF32_t) -> c_int; ... | 1644 | | 1645 | | } | |_^ | = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! = note: for more information, see issue #123743 <https://github.com/rust-lang/rust/issues/123743> = note: `--force-warn missing-unsafe-on-extern` implied by `--force-warn rust-2024-compatibility`
The text was updated successfully, but these errors were encountered:
Fixed Rust plugin output to adhere to RFC3484. See anderslanglands#15.
03d9ce1
unsafe
Huh, interesting. Does it still build correcly in 2021 with the unsafe added?
Sorry, something went wrong.
Yes it does.
No branches or pull requests
The
babble
Rust plugin should emitunsafe extern "C"
blocks instead of justextern "C"
.See RFC 3484.
A specific error when running
cargo fix --edition
on a Rust 2021babble
project looks like this:The text was updated successfully, but these errors were encountered: