Menu
Search

Forums

Forum Index

August 22, 2016
Gravatar of Alexandru ErmicioiPosted by Alexandru ErmicioiReply
Alexandru Ermicioi
Gravatar of Alexandru Ermicioi


Reply
Good day.

In current implementation of dmd/ldc/gdc, does this trait guarantee, that the order of elements returned in tuple, is same, in several calls of it on same Type and member?

Also, is guaranteed that in future versions of dmd, the order of elements won't change?
August 22, 2016
Gravatar of Lodovico GiarettaPosted by Lodovico Giaretta
in reply to Alexandru Ermicioi		Reply
Lodovico Giaretta
Gravatar of Lodovico Giaretta
Posted in reply to Alexandru Ermicioi


Reply
On Monday, 22 August 2016 at 12:14:41 UTC, Alexandru Ermicioi wrote:
> Good day.
>
> In current implementation of dmd/ldc/gdc, does this trait guarantee, that the order of elements returned in tuple, is same, in several calls of it on same Type and member?
>
> Also, is guaranteed that in future versions of dmd, the order of elements won't change?

The official spec [1] does not state anything about this, but for other similar traits it says that the order is not defined and should not be relied upon, so I'm inclined to think that getOverloads works that way too.

Definitely worth an enhancement request, to document this thing.

[1] https://dlang.org/spec/traits.html