On Friday, 1 August 2014 at 17:06:24 UTC, Daniel Murphy wrote:
"Dicebot" wrote in message
news:[email protected]...
I am afraid we don't have the right way in D then. Caring
about cross-module name conflicts feels too much like plain C.
But with overloading!
It isn't just about avoiding conflicts - if the function name
is unique, you can tell what the code is doing without having
to examine the context so closely. This is especially
important for the standard library, because the time spent
learning names can be reclaimed over multiple projects.
If you find this important, you can always require renamed /
static imports in your projects. On the contrary, if function
name is already qualified with some redundant information, there
is no simple way back other than aliasing all symbols from that
module.
I am convinced we are missing good style of using D import
system, not good names.
This is a strength of C, although C goes way too far with
forcing it.
There are surprisingly many things I miss from C but manual name
mangling is not in that list.
