lolbinarycat

why not just forbid manually implementing `Default` on structs with field defaults? that gets around the nasty `..Default::default()` parity issue, and is a restriction that can be relaxed in the...

> I wasn't trying to solve that, so in my proposal `a: i32 = 17` would take precedence over `impl Default` on the same struct when `S { .. }`...

It still mentions it: > You can also quickly discover and list other users with: ```bash cargo crev repo fetch url https://gitlab.com/crev-dev/auto-crev-proofs cargo crev repo fetch all cargo crev id...

hmm, [the async book](https://rust-lang.github.io/async-book/08_ecosystem/00_chapter.html#async-runtimes) isn't super clear about this. it says that executors are responsible for polling futures (which lines up with the std::task documentation, which seems to consider anything...

even if "all executors can handle multiple tasks" is true, this is still overgeneral, since the executor could use some other non-queue datastructure like a red-black tree (such as the...

i guess, but the phrasing is pretty confusing. specifically, the usage of "are allowed to" instead of "always will". the example also doesn't make it clear that order doesn't matter.

cleaned up the formatting a bit, hopefully this satisfies tidy

> I can't say that I like that comma. If it's tough to get rid of it (I think it would be, since it would require infinite lookahead to distinguish...

ah, that makes sense. we should probably document that behavior somewhere. i mean... if we're going treat spaces as :: in that case, we should probably do it here too,...

Another approach would be adding proper boolean combinators to rustdoc-search, that way we could just do `add & u8 -> u8`, however, that would be significantly more involved, and might...