Begin rant.

When a programming language has an edge (not even a corner) case commonly requiring the direct expression by the developer of types like,

core::iter::Zip<core::iter::FilterMap<'_, (&std::collections::hash::set::HashSet<attr::Attribute>, &attr::Attribute), &attr::Attribute, core::iter::Zip<core::iter::Repeat<&std::collections::hash::set::HashSet<attr::Attribute>>, core::iter::Map<', (&attr::Attribute, &()), &attr::Attribute, std::collections::hash::map::Entries<', attr::Attribute, ()>>>>, core::iter::FilterMap<', (&std::collections::hash::set::HashSet<attr::Attribute>, &attr::Attribute), &attr::Attribute, core::iter::Zip<core::iter::Repeat<&std::collections::hash::set::HashSet<attr::Attribute>>, core::iter::Map<', (&attr::Attribute, &()), &attr::Attribute, std::collections::hash::map::Entries<'_, attr::Attribute, ()>>>>>,

how does fixing this not take the absolute highest priority?

>>32
You can even do stuff like

import qualified Shit.Piss.Negroes.Tongue.Anus.Unzip.Before.Fucking.Anus as A
import qualified Shit.Piss.Negroes.Tongue.Anus.Unzip.Before.Fucking.Vagina as A
import Shit.Piss.Negroes.Tongue.Anus.Unzip.Before.Fucking.Vagina (gSpot)

That way, provided there are no name clashes, you can call shit from both Anus and Vagina as A.foo. Also you can call Vagina's gSpot as just gSpot (as well as A.gSpot, of course).

Yeah, let's not forget that a module system must check for possible name clashes. Namespaces, at least in C++, are a mess where nobody gives a shit if you import a name that clashes with one you've defined.