Razvan Nitu
Razvan Nitu
I would argue we should commit to 100%. The spec currently does not specify anything about shallow vs. deep, rather that __FUNCTION__ and other special function are evaluated at the...
@pbackus I think that keeping the needle at 0% is not the behavior users expect. This causes reports such as [1][2] and many other duplicated/sightly modified examples. The current design...
@WalterBright I take it you agree with this addition?
@ibuclaw The template work is unblocked. If I understand correctly, #14309 is going to make this redundant.
The behavior in the presence of imported overload sets needs to be defined: ```d // a.d void foo(int); void foo(string); // b.d void foo(); // c.d import a; import b;...
Also, please add "Fix" in the commit message so that the bot auto-closes the issue if this gets merged.
@FeepingCreature I've tested a bit locally and this seems to be a problem only if the overload set is defined and used in the same module. For example, this works:...
I agree, it's just that I wonder if this form of `getOverloads` is not susceptible of introducing weird edge cases. I guess the question is: how often do we find...
@FeepingCreature Please add this test case: ```d // a.d void foo(int); void foo(string); // b.d void foo(); // c.d import a; import b; __traits(getOverloads, foo); // which one?! ``` And...
cc @WalterBright @atilaneves as these is a new language addition.