This looks really exciting, but I'm not clear on how this works:
So what has happened here? Riff has:
- read your project’s Cargo.toml,
- determined which external dependencies
are necessary based on your crate
dependency graph,
How does Riff go from crate -> external package dependencies? Are those listed in the Cargo.toml somewhere? Does it just make a best-effort attempt to scrape the project and figure out what's referenced? Or does Riff maintain its own internal registry of which dependencies are needed by which popular crates?