• IchorDev (3/3) Jul 13 2023 I've noticed that `__traits(getOverloads)` always returns the
• Dennis (11/14) Jul 13 2023 No. It depends on the order the compiler analyzes the symbols,
• IchorDev (6/20) Jul 13 2023 Well that makes sense, but also wouldn't apply to the use-case
• Dennis (3/6) Jul 13 2023 The order is not guaranteed. I don't know why you need a specific

IchorDev <zxinsworld gmail.com> writes:

I've noticed that `__traits(getOverloads)` always returns the 
overloads in lexical order across DMD, LDC, and GDC. Is this 
reliable at all?

Dennis <dkorpel gmail.com> writes:

On Thursday, 13 July 2023 at 08:03:02 UTC, IchorDev wrote:
 I've noticed that `__traits(getOverloads)` always returns the 
 overloads in lexical order across DMD, LDC, and GDC. Is this 
 reliable at all?

No. It depends on the order the compiler analyzes the symbols, 
which is often lexical order, but it can vary based on static if, 
mixin, forward references etc. Here's a counter example:

```D
        void f(int  x);
mixin("void f(float y);");
        void f(char z);
```

Here you get overloads of `f` in the order (x, z, y) instead of 
(x, y, z).

IchorDev <zxinsworld gmail.com> writes:

On Thursday, 13 July 2023 at 10:53:49 UTC, Dennis wrote:
 On Thursday, 13 July 2023 at 08:03:02 UTC, IchorDev wrote:
 I've noticed that `__traits(getOverloads)` always returns the 
 overloads in lexical order across DMD, LDC, and GDC. Is this 
 reliable at all?

 No. It depends on the order the compiler analyzes the symbols, 
 which is often lexical order, but it can vary based on static 
 if, mixin, forward references etc. Here's a counter example:

 ```D
        void f(int  x);
 mixin("void f(float y);");
        void f(char z);
 ```

 Here you get overloads of `f` in the order (x, z, y) instead of 
 (x, y, z).

Well that makes sense, but also wouldn't apply to the use-case 
that I was considering, since all the code would be in one mixin. 
However, the spec doesn't specify that this is how `getOverloads` 
**must** work; is this guaranteed behaviour but the spec simply 
omits it?

Dennis <dkorpel gmail.com> writes:

On Thursday, 13 July 2023 at 11:04:40 UTC, IchorDev wrote:
 However, the spec doesn't specify that this is how 
 `getOverloads` **must** work; is this guaranteed behaviour but 
 the spec simply omits it?

The order is not guaranteed. I don't know why you need a specific 
order, but perhaps you can sort based on `__traits(getLocation)`.