Stricter Assignability Checks for Overloaded Functions

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ --> ## Search Terms <!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily --> function overload, assignability ## Suggestion <!-- A summary of what you'd like to see added or changed --> When a function has overloads, each with a different number of arguments, subtle bugs can occur. My suggestion is to have extra assignability checks for overloaded methods/functions. When assigning `A` to `B` the algorithm should be, 1. Is `A` assignable to `B` under the existing assignability rules? 1. Is `A` an overloaded function/method? 1. If it is not, we are done. 1. If it is, we need more checks, 1. Does the assignable overload of `A` have the same number of arguments as `B`? 1. If it does, we are done. (Right? Maybe?) 1. If it doesn't, find all overloads of `A` with the same number of arguments as `B` 1. Is each overload assignable to `B`? If it isn't, we have a compile-time error ## Use Cases <!-- What do you want to use this for? What shortcomings exist with current approaches? --> Better type safety. I've been bitten by this behaviour regarding overloaded functions/methods in the past, with far more complicated examples. My general advice to people is to avoid overloads as much as possible/at all cost. If this hole in the type system is fixed, I may not be so averse to overloads... Or I'll probably find something else to gripe about =x ## Examples The repro below has the following properties, + Each overload has a different number of arguments + Each…