ADL
Walter Bright via Digitalmars-d
digitalmars-d at puremagic.com
Sat Sep 3 13:39:29 PDT 2016
On 9/3/2016 9:01 AM, Manu via Digitalmars-d wrote:
> Right, and it also has to not conflict with possible local
> definitions, or instances supplied by imports in the local namespace.
> Ie, the module where T came from is *an additional* place to look, not
> *the* place to look.
> I expect that local definitions may exist for things like generic
> fallbacks, or primitive/builtin type implementations.
1. 'alias func = ...;' also works to bring in local definitions to an even
footing with the other alias func statements.
2. Due to recent changes to import lookup rules, imports are searched if locals
do not satisfy the lookup.
3. You can use traits(compiles, ...) to not insert the names in the local scope
if it already can be looked up.
So I believe you're good to go.
More information about the Digitalmars-d
mailing list