Michal 'vorner' Vaner
Michal 'vorner' Vaner
Yes, of course (eventually). But I expect to do it the same way I do everything else ‒ call the [`sin`](https://doc.rust-lang.org/std/primitive.f32.html#method.sin) on each lane in a for cycle and construct...
> Basically any function that wont be inlined won't even be eligible for the auto-vectorizer to look at it. That shouldn't be a problem. The primitive types' `sin` and similar...
Seems I've again learned something. I've assumed that the x86_64 assembler has special instructions for sin and also for vectorized sin and indeed, then I'd expect the compiler would change...
Hello I guess the „proper“ way to fix it will be hard and will take time (I'm not sure if reordering the calls inside the `StructOptInternal::augment_clap` to call these after...
I've figured that, but it is kind of bad for structs provided by libraries. I want to have doc comment to render on [docs.rs](https://docs.rs), I also tend to `#[warn(missing_docs)]`. But...
Just for the record, I've figured a workaround that keeps them for the docs.rs, but doesn't hijacks them for the about: ``` #[cfg_attr(not(doc), allow(missing_docs))] #[cfg_attr(doc, doc = r#" The doc...
Um, I don't really understand what the problem is. I mean, this guide is kind of dense and expects you already know a lot (like, how to use tokio). But...
I admit, I haven't paid attention much to how the docs changed over time, but yes, I think internals sounds about right. And maybe stating that this part is kind...
Internal reference: BFW-5038
Internal reference: BFW-5040