It would break semantics if overloads are allowed in a way that is syntactically valid in older code. So the challenge would be to pick syntax to specify the type signatures that can not occur in old working code.
Finding syntax that doesn't look awful but that is currently invalid would actually likely be the hardest part of adding support for it.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.