there's a lot of arguments for and against this, but i think a lot of these don't matter, because many crates are already shipping prebuilt artifacts. ideally this could also be integrated with some sort of deterministic build system. the simplest implementation would be a per-crate (not per package) table that maps a target triple and a rust version (may be ignored for crates with a stable ABI or ones that are cli-only) to a hash and url for that crate's output. may need another layer of nes...| Rust Internals
They can: fn main() { let mut foo = Vec::new(); let bar: &mut Vec = &mut foo; std::panic::catch_unwind(std::panic::AssertUnwindSafe(move || { bar.push(42); panic!(); })).unwrap_err(); assert_eq!(foo[0], 42); println!("Mutable reference crossed panic boundary"); }| Rust Internals
Please add support for generating markdown files from rust documentation comments. By generating markdown files, we can easily add these files to our github projects as the documentation of the project and these markdown files are simple in syntax and can be read on github within the browser like any other README.md file is for any github repo.| Rust Internals