Lokathor
Lokathor
I've marked this as "good first issue". I don't think that a contributor would solve this all in a single PR, but doing this for a module at a time...
Small update: if we put the intrinsic function name in square brackets with backticks (updated in the above) then we'll get intra-doc links to the `core::arch` function. Might as well.
Oof, we got a mild problem @joshtriplett, rustdoc search **doesn't** search the body of docs, only names, params, and return types. So if you say in a function's docs ```rust...
Yeah I'll continue to slowly add the info as I go and hope for rustdoc search functionality to catch up some day.
https://github.com/BLAKE3-team/BLAKE3
Working examples count as docs, in a sense, so we'll add that label.
The problem here is that [array_vec!](https://docs.rs/tinyvec/latest/tinyvec/macro.array_vec.html) has several ways it can be invoked. ```rust macro_rules! array_vec { ($array_type:ty => $($elem:expr),* $(,)?) => { ... }; ($array_type:ty) => { ... };...
I'm not against it, but I wonder if you can convince std to put this on vec in nightly
hmmmmmmmmm how much of this impacts rebuild times when the crate is used as a dep? I do want fast builds, but I think that if only the initial build...
Ah, so it's not quite like normal generics where the monomorph cost of the code is paid by the downstream crate each time it rebuilds?