https://issues.dlang.org/show_bug.cgi?id=9631
Andreas Reischuck <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #11 from Andreas Reischuck <[email protected]> --- I tried to tackle this issue at DConf Hackathon. The issue is not totally trivial. Fully qualifying all types in error messages leads to unreadable error messages. Imagine a function with 5 arguments, where each argument is fully qualified. The good solution would be to detect that the error message is ambiguous and only then fall back to fully qualified types. To do this each error has to be inspected separately. Some are more complicated, as types of expressions and arguments are generated independently right now. I suggest to split this issue and create issues for all the situations types are reported to be ambiguous and tackle them one by one. Solving them all at once is quite an endeavor. --
