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?

>>42
Unnecessarily yet pleasantly, yes?

>>41

You need to be able to canonicalize in the case of aliases

The compiler does. I don't. There aren't any practical cases where all the imported modules can't be aliased with one-two letter qualifiers. No need to write Data.Map.Map when just M.Map will do.