On Thursday, 29 September 2016 at 16:30:56 UTC, Eugene Wissner
wrote:
The problem is you can never know all the use cases of some
feature. It is just pointless to try to predict where a user
will need a feature. I had a use case where I could be sure
that everything needed is imported and where I could save
compile time and make the function signatures a bit simpler.
Let us just remove fullyQualifiedName from the language. Why
spend effort with it? Why should one write into the
documentation: Oh, you thought it would work? How funny! This
function is just for fun of the library creators and is only
good to pass it to writeln(), it isn't supposed to work.
The point is that the fullyQualifiedName of something is not
always enough to generate that type.
As you have seen in your usecase.
