Re: [swift-users] Two Obj-C visible functions no longer overload?

It’s always been possing to make arrays of Error, but exposing those arrays back to Objective-C may or may not have worked correctly (as you noticed). And yes, your solutions are either adding different labels, or using the ‘objc’ attribute to explicitly specify a selector for one or the other.

Re: [swift-users] Two Obj-C visible functions no longer overload?

Jordan: Could you expand on allowing making arrays of errors? AFAIK, making arrays of ErrorProtocol/ErrorType/Error has always been possible. And somewhat coincidentally I ran into a runtime issue with the same library, fixed in the latest Swift trunk package, that would result in a

Re: [swift-users] Two Obj-C visible functions no longer overload?

I would definitely expect these two to conflict, so if they previously compiled happily I would guess that’s a bug we fixed. The most likely possibility is that we didn’t allow making arrays of errors and now we do. Jordan > On Aug 5, 2016, at 14:57, Jon Shier via swift-users

Re: [swift-users] Two Obj-C visible functions no longer overload?

On 5 Aug 2016, at 22:57, Jon Shier via swift-users wrote: > Now, if I mark one of the functions @nonobjc, it compiles. So is this a bug > or change in behavior? NSOperation has a property with `-finished:` as the setter and `-isFinished` as the getter. It’s not