Ambiguity when a method signature with a default-value parameter matches another method signature?

This is a very dangerous move. The API can change its default value, which will not be reflected in the fixed version.

That actually wouldn't work if the function has multiple defaulted values.


Using type inference to decide between two signature is so ingrained on Swift. I'm not sure there's a good solution that uses only existing call syntax and/or without changing the type inference rule.