Hadrien G.

Seems so, at least I'm observing a case where ArrayViewMut::split_at is not inlined as of Rust 1.70.

> It sounds like you use rayon::iter::split. Take note that ndarray already implements split-based parallelism natively using rayon, in that case see Zip and parallel in the docs. 🙂 I...

Indeed, I regularly set codegen-units = 1 in my performance-sensitive projects in order to work around lost inlining of important std methods like `Iterator::fold()`, or just to make the performance...

@CAD97 Since you also asked your question about compiler flags in the irlo thread, I replied to it there. The short answer is that no, I am not using -Zshare-generics...

> There's a bunch of method calls used used between ArrayViewMut::split_at and RawViewMut::split_at that look like small methods that should be #[inline]. > However the main logic is implemented in...

I fear the semantics mismatch between unsafe-means-trusted and unsafe-means-unchecked is by now a syntactic wart engraved in Rust that we will need to accept living with forever... The question we...

To put my questions in pseudocode... ```rust // Question: Can a trait definition afford not to care about impls being unsafe-ready? pub trait Iterator { type Item; fn next(&mut self)...

After closer investigation, `--raw-line` can be used to inhibit the lint quite easily, so the only remaining question is, should bindgen make it the default.

I agree that the current codegen for opaque types is unnecessarily dangerous and should be changed to follow the current nomicon guidelines.

See also https://github.com/rust-lang/rust-bindgen/issues/2767 .