2 ms·
> Yes, but then you introduce new scope. If shard1::Foo depends on shard2::Foo, you then end up with a murder of import statements at the top of every file. Wa
by littlestymaar 6y ago
> Yes, but then you introduce new scope. If shard1::Foo depends on shard2::Foo, you then end up with a murder of import statements at the top of every file.
Wait, what? Import statements are recursive in Rust, if shard1::Foo depends on shard2::Foo, you just need to manually import shard1::Foo.
- q3k 6y agoOf course. I mean importing shard2 within shard1. You can always `use super::*` but, ugh. And with most imports in Rust being unqualified (that seems to be the idiomatic approach), I then find it difficult to differentiate types that are from a sibling, internal module from types that are important from external crates. Especially at site of use of the type. Go's “local package names unqualified, everything else qualified” makes it much easier for me to read code without first having to parse all the import statements.