#Is it normal for some clippy errors to only show up on specific targets triples?

1 messages · Page 1 of 1 (latest)

tulip parrot
#

Is it normal for some clippy errors to only show up on specific targets triples?

#

A couple times in the past I've seen clippy warnings that only showed up on wasm32-unknown-unknown, even though the code didn't change depending on target. There was no cfg(...) in the immediate vicinity of where the warning appeared.

#

Most recently I've seen clippy warnings appear when run on Linux, but not on macOS, with the same versions of Rust.

pine tartan
#

No, I would suspect that it wasn't the same rustc versions between the targets. What warning? If you have one at hand

#

There was some new lints stablized in the last 2 updates to stable so I have seen people with newer CI containers than their local build get new lints they didn't expect