https://issues.dlang.org/show_bug.cgi?id=19569
RazvanN <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #18 from RazvanN <[email protected]> --- (In reply to Manu from comment #16) > Oh wow... interesting. > I think I have broken code floating around :/ > > So, is the issue here that it's possible to emit 2 functions that have > ambiguous distinction, but no compile error? > If a nothrow function can call either one, then it probably shouldn't just > pick one, but rather emit an ambiguous call error instead? But it doesn't pick one randomly, it picks the "better one" which is the one that is pure/@safe/nothrow/@nogc --
