is duplicated by:

• SR-1857 Using PHFetchResult.enumerateObjects() with trailing closure syntax causes compiler error
• SR-2425 NsMutableIndexSet Enumerate Issue

relates to:

• SR-2838 renamification creates ambiguity
• SR-3550 Compound name syntax for functions with no params

Issue Description:

The following code doesn't compile in any recent toolchain, due to issue with renamification and the rules for Swift default parameters:

            let pep = ["Manny", "Moe", "Jack"] as NSArray
            let ixs : NSIndexSet = pep.indexesOfObjects(passingTest: {
                (obj:AnyObject, ix:Int, stop:UnsafeMutablePointer<ObjCBool>) -> Bool in
                return true
            })

Basically it is now unnecessarily difficult to call NSArray indexesOfObjects. The reason is that Swift sees the passingTest: parameter as ambiguous. Now, you might say: huh? Ambiguous with what? Well, it's rather subtle. Here's the detailed complaint from the compiler:

Foundation.NSArray:77:17: note: found this candidate

    public func indexesOfObjects(passingTest predicate: (AnyObject, Int, UnsafeMutablePointer<ObjCBool>) -> Bool) -> NSIndexSet

Foundation.NSArray:80:17: note: found this candidate

    public func indexesOfObjects(_ opts: NSEnumerationOptions = [], passingTest predicate: (AnyObject, Int, UnsafeMutablePointer<ObjCBool>) -> Bool) -> NSIndexSet

The nameless parameter in the second method has a default value, and both methods have a `passingTest` parameter, so in the absence of further information, our code could now be calling either of them.

This analysis suggests (rightly) that we can worm our way out of the difficulty by saying:

            let ixs : NSIndexSet = pep.indexesOfObjects([], passingTest: {
                (obj:AnyObject, ix:Int, stop:UnsafeMutablePointer<ObjCBool>) -> Bool in
                return true
            })

Yecch! What is the point of having an optional parameter (a parameter with a default value) if you have to supply it anyway? How did we get ourselves into this mess in the first place?

The answer is that Objective-C has two perfectly separate methods:

    indexesOfObjectsWithOptions:...

and

    indexesOfObjectsPassingTest:...

A moment's thought will reveal that Swift renamification has conflated these two methods into one. It is therefore impossible to call indexesOfObjectsPassingTest — it is effectively stricken from the field. Only indexesOfObjectsWithOptions can be called.

This could easily be resolved by giving the options parameter an explicit label. We would then have indexesOfObjects(options:... ) and indexesOfObjects(passingTest:... ) and all would be well.