Wow, and someone else just yesterday was giving D credit for not thrusting everything into the global name space like C does!
Yes, two different D modules can declare the same name as public, and they will not conflict with each other.
Yes, two different D modules can declare the same name as public, and they will not conflict with each other.
It wasn't about name clashing, but readability. It's not clear at first glance what functions belong to which imports.
As an example: https://tour.dlang.org/
Three imports and what appear to be four unqualified functions from them.
Or just use static import.
Well, the developer wrote `import thing;` instead of either `static import thing;` or `import thing : specific, list;` so it was their decision.