https://issues.dlang.org/show_bug.cgi?id=18866
Paul Backus changed:
What|Removed |Added
CC||snarwin+bugzi...@gmail.com
--- Comment #8 from
https://issues.dlang.org/show_bug.cgi?id=18866
Iain Buclaw changed:
What|Removed |Added
Priority|P1 |P3
--
https://issues.dlang.org/show_bug.cgi?id=18866
Mike Franklin changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
https://issues.dlang.org/show_bug.cgi?id=18866
--- Comment #7 from John Hall ---
I get that. The point I wanted to highlight was that even if it's not changed
at least the spec can be beefed up.
--
https://issues.dlang.org/show_bug.cgi?id=18866
--- Comment #6 from Simen Kjaeraas ---
(In reply to John Hall from comment #5)
You're right that a new global function will shadow opDispatch, but with the
fix the exact opposite problem will appear, so it's not all that simple.
--
https://issues.dlang.org/show_bug.cgi?id=18866
John Hall changed:
What|Removed |Added
CC||john.michael.h...@gmail.com
--- Comment #5 from
https://issues.dlang.org/show_bug.cgi?id=18866
--- Comment #4 from Simen Kjaeraas ---
> there would be absolutely no way of calling fun1() from within the
> WithStatement body
Sure there would. Assuming the same code as in comment 0, you would call the
global fun2 using .fun2();. You can test t
https://issues.dlang.org/show_bug.cgi?id=18866
RazvanN changed:
What|Removed |Added
CC||razvan.nitu1...@gmail.com
--- Comment #3 from Razv
https://issues.dlang.org/show_bug.cgi?id=18866
--- Comment #2 from Mike Franklin ---
Or actually it may be this PR that introduced the issue:
https://github.com/dlang/dmd/pull/6439
--
https://issues.dlang.org/show_bug.cgi?id=18866
Mike Franklin changed:
What|Removed |Added
CC||slavo5...@yahoo.com
--- Comment #1 from Mike
10 matches
Mail list logo