Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-8725] AnyObject Constraints Do Not Participate in Overload Resolution #51236

swift-ci opened this issue Sep 10, 2018 · 2 comments


Copy link

swift-ci commented Sep 10, 2018

Previous ID SR-8725
Radar None
Original Reporter mdmorris (JIRA User)
Type Bug
Additional Detail from JIRA
Votes 1
Component/s Compiler
Labels Bug, TypeChecker
Assignee None
Priority Medium

md5: fd60ebca177c5310df43da5a61db8ade

Issue Description:

AnyObject constraints do not participate in overload resolution, as such an overloaded generic function whose type parameters differ only by an AnyObject constraint, where neither function is a subtype of the other, will cause an "ambiguous use" error when attempting to use the more constrained function.


public func with<T>(_ initial: T, update: (inout T) throws -> Void) rethrows -> T {
    var copy = initial
    try update(&copy)
    return copy

public func with<T: AnyObject>(_ object: T, update: (T) throws -> Void) rethrows -> T {
    try update(object)
    return object

let x = with(1) {
    $0 += 2
    $0 *= 5
    $0 -= 1

final class Thing {
    var name: String = ""
    var position: (Int, Int) = (0, 0)

let y = with(Thing()) { // Ambiguous use of `with(_:update:)`
    $ = "Goblin Bandit"
    $0.position = (13, 2)
Copy link

belkadan commented Sep 11, 2018

cc @rudkx, @DougGregor

Copy link
Collaborator Author

swift-ci commented Jan 23, 2022

Comment by Michael D. Morris (JIRA)

Okay, I don't know if this is new, but even though the test case above still has an ambiguity error, this works (Swift 5.5 Linux):

func foo<T>(_ value: T) {

func foo<T: AnyObject>(_ object: T) {
    print("foo<T: AnyObject>(\(object))")

final class Class {


do {

So, maybe this bug only applies when type checking closure parameters?

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants