dependency graph is a beautiful name for a baby girl

imo it should go a step further and instead of being `or_panic` and `or_panic_with(“msg”)`, it should be `or_panic(“msg”)` and `or_panic_without_msg` to encourage explanations of why it’s fine to panic. i know it goes against normal naming conventions but i think it’s fine

i’ve only ever got ~250GB from this, but i’m also only working on the closed-source version, so yours is probably mostly the oss version

right, but i meant like “rustdoc available locally for all crates on crates.io”

is this gonna be a fully-local docs.rs

i like seoul256 rn: github.com/junegunn/seo...

but used to rly be into oldworld: github.com/dgox16/oldwo...

need to add a new “closed - yaayyy!!” option

i’ve always thought Result<T, !> should be used for indicating potential panics. that way you have to essentially acknowledge, at the call site, that there could be a panic, but it doesn’t really get in your way since you can just `let Ok(val) = func();`

This seems basically the same as running `cargo downgrade -p <package> --precise 0.7.0-rc.1` - what reason would there be to use this python script instead?

real

hell yea, you should definitely share when you get started on that. i would love to see what that process is like

yeah, i’ve seen some really crazy layouts online - i really wish i was a keyboard person cause they seem so much fun to tinker around with but i feel like i have way too many other things stealing my attention rn :(

any particular kits you’re looking at, though?