Yes, it has to do with how its type inference interacts with certain language features (particularly return type overloading).

It's unfortunate but I would honestly be ok with a "strict mode" that requires extra annotations from the programmer if it would prevent this stupid error in practice.