Module function conflicting with reserve function

[Stanislav Blinov]

On Tuesday, 6 November 2018 at 21:19:29 UTC, Peter Campbell wrote:

> Given your second example that makes me think that, because 
> object functions are provided by the runtime without me 
> explicitly importing it, this is likely only an issue for 
> object functions? Or can this behaviour happen with any free 
> functions with the same name but completely different parameter 
> types?

Not with completely different parameter types, no. But it can 
happen with functions imported from different modules, as they're 
from different overload sets. There's an example in that Overload 
Sets section of the spec.