3 ms·
Cargo.toml isn't in language. It's for the package manager and the build tool. The language shouldn't be married to either thing. As for dropping extern crate,
by qwertyuiop924 10y ago
Cargo.toml isn't in language. It's for the package manager and the build tool. The language shouldn't be married to either thing.
As for dropping extern crate, it either marries rust to cargo, or it makes imports implicit. Neither is desirable.
- tatterdemalion 10y agoOne possibility is for rustc to take extern crate declarations as commandline args and for cargo to invoke them based on what's in the toml.
- Manishearth 10y agoThis technically already happens
- deleted 10y ago[deleted]
- tatterdemalion 10y agoRight, I guess there's no info needed outside what the --extern flag contains.
- themihai 10y agoYou have modules, use, extern, cargo.toml, cargo.lock. It looks quite verbose and redundant to me. I expected it to simplify but moving more to config files seems a backwards step. I may be biases but I find the Go import/packing vastly superior in terms of usuability(i.e using a single import statement you make the import explicit and ready to use). I think the trick is to build the tools on top of the source code not on top of config files(i.e ala C/C++).