Redeclaring members in an extension hides the original member *sometimes*. Why?

Question

By chance, I discovered that you can do this without the compiler complaining:

extension Date {
    var timeIntervalSinceNow: TimeInterval {
        return 1000
    }
}

What's weirder, is that this actually evaluates to 1000:

Date().timeIntervalSinceNow

• The extension seems to hide the original member.

So I tried to do this with my own class:

class A {
    var a: String {
        return "A"
    }
}

extension A {
    var a: String {
        return "a"
    }
}

• and it fails to compile: "invalid redeclaration of 'a'".

I observed that this does not affect the usage of the original member through a protocol, which is expected behaviour of hiding:

extension Date {
    var description: String {
        return "XXXX"
    }
}

let date: CustomStringConvertible = Date()
date.description // normal date

Date().description // "XXXX"

Can you explain why does the bullet pointed phenomena occur?

Fiction

Could it be that Date is probably a wrapper around the old Objective-C NSDate while your class/extension A are pure Swift? – Baloney

I tried to make A a subclass of NSObject and the same error appears, so I don't think that's the reason. @Baloney – Fiction

Modules. You can override like this across modules. No idea how to access the original member, though. – Irritated

Same class extension in two different modules – Irritated

@Sweeper: This is a bug, see matt's comment here: #33862914. – Pinzler

Answer 1

This works because you are declaring this extension in a separate module from the original variable declaration.

Across modules a variable name can be overloaded but in my mind this has been a shortcoming of Swift as there is currently no way to explicitly state which module declaration it is that you want.

Shakhty

Is this behaviour documented anywhere? – Fiction