Should we really rank overloads found through AnyObject lookup?

[hamishknight]

There was actually a pitch to deprecate AnyObject lookup, which I would support:

Pitch: Deprecate/remove AnyObject method dispatch

Hi all, Dynamic dispatch of methods through AnyObject is a source of implementation complexity, has many known bugs which we are not going to fix, and no longer makes sense now in an id-as-Any world; AnyObject is not the ‘common currency’ type for arbitrary Objective-C objects anymore. I would like to propose we deprecate it as follows: - Unconditional warning in Swift 4.1, with a fixit to add an ‘as’ cast to cast the base value to the right type - Error in Swift 5 in -swift-version 5 mode T…

@Slava_Pestov Is there any possibility of re-visiting this in the Swift 5 timeframe?