You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test.rs:2:1: 2:47 warning: code is never used: `start`, #[warn(dead_code)] on by default
test.rs:2 fn start(_argc: int, _argv: **u8) -> int { 0 }
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
despite the start function being generated and exported. Servo hits this warning in src/components/main/servo.rs.
The text was updated successfully, but these errors were encountered:
I was just confused by Servo's workaround for #13905, which involves building the same .rs file with two different crate types, and thought that the dylib also contained the start function.
fixrust-lang#14034
The currect implementation of `obfuscated_if_else` sometimes makes
incorrect suggestions when the original code have side effects (see the
example in the above issue). I think this can be fixed by changing the
applicability depending on whether it can have side effects or not.
changelog: [`obfuscated_if_else`]: change applicability when the
original code can have side effects
Running
rustc --crate-type=dylib test.rs
ongives the warning
despite the start function being generated and exported. Servo hits this warning in
src/components/main/servo.rs
.The text was updated successfully, but these errors were encountered: