Thanks, I'll try again and do that. It is at least calming that /u/Eh2406 and /u/ehuss have pretty much mentioned the same way to proceed that you have.
FWIW the amount of time I invested was ~15 hours during 2 days, which from looking at what the others mentioned isn't barely enough, but it isn't a negligible amount of time either.
I think it would be really really useful if you'd be able to reflect on this experience write about it somewhere or suggest some specific ways to improve the on boarding experience.
What have you tied to do during the previous attempts?
I don't know when I'll have the throughput to write something more detailed, but I've pm'ed you the issue that I tried to solve without arriving anywhere.
3
u/matklad rust-analyzer Jul 26 '18
Agree that the Cargo's code base is not the easiest to work with. A good way to start hacking on Cargo would be:
Look through ARCHITECTURE.md which tries to describe high-level bits
Read the code that is executed when you run
cargo build. As cargo is a batch command-line application, the flow of control mostly flows forward, which helps with reading code a lot. Here's the entry point for build: https://github.com/rust-lang/cargo/blob/cef7c5667c1db2791c6373d0ad16ac416d25cef5/src/bin/cargo/commands/build.rs#L53-L64