In some irritating circumstances, the load order can cause a +load message to trigger other code, which sends messages with selectors that have not been mapped yet.
The runtime was handling the message lookup correctly in this case, but only as a side-effect of the fallback code from when type-dependent dispatch is not possible. This resulted in a confusing warning message, telling you that you were calling a method with an incorrect signature, when the two signatures that it printed were the same. This case is now handled correctly, so the warning disappears (unless you really are calling a method with the wrong signature and have TDD enabled).main
parent
e9b129d878
commit
42a545fc7c
Loading…
Reference in New Issue