mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-22 23:04:33 +00:00
c8b76bcf58
On some architectures, vector types may have a different ABI depending on whether the relevant target features are enabled. (The ABI when the feature is disabled is often not specified, but LLVM implements some de-facto ABI.) As discussed in rust-lang/lang-team#235, this turns out to very easily lead to unsound code. This commit makes it a post-monomorphization future-incompat warning to declare or call functions using those vector types in a context in which the corresponding target features are disabled, if using an ABI for which the difference is relevant. This ensures that these functions are always called with a consistent ABI. See the [nomination comment](https://github.com/rust-lang/rust/pull/127731#issuecomment-2288558187) for more discussion. Part of #116558
16 lines
338 B
Rust
16 lines
338 B
Rust
//@ known-bug: #131342
|
|
|
|
fn main() {
|
|
let mut items = vec![1, 2, 3, 4, 5].into_iter();
|
|
problem_thingy(&mut items);
|
|
}
|
|
|
|
fn problem_thingy(items: &mut impl Iterator<Item = u8>) {
|
|
let mut peeker = items.peekable();
|
|
match peeker.peek() {
|
|
Some(_) => (),
|
|
None => return (),
|
|
}
|
|
problem_thingy(&mut peeker);
|
|
}
|