This is going to seem a little bit stupid I am sure. I understand that
extern does something specific. But wouldn’t it not be possible to wrap it functionality up with
extern seem to load an external library, while
use can bind a specific point in the path. I would thin you could combine them so you can just write use
lib::mod. If it isn’t loaded then the compiler just loads it. Or have the compiler autoload libraries found in a certain directory and the cargo build system could handle downloading the dependencies. If not using cargo load the libraries in the root of the src file being compiled or something like that
I guess it isn’t a big deal. It just seems like a good amount of extra code as it seems every
extern has at least 1 if not more
use's. Because everyone like shorter paths.