Protocols need to use String(self) rather than String(Self) about reusable

[AliSoftware]

@rollandjb Are you sure about this?

I just tested this in a playground, so it seems to work as expected even with Self:

protocol Reusable {
  static var reusableIdentifier: String { get }
}

extension Reusable {
  static var reusableIdentifier: String {
    return String(Self)
  }
}

class ParentView: Reusable {}
class ChildView: ParentView {}

let ri = ChildView.reusableIdentifier
print(ri) // prints "ChildView", as expected

[rollandjb]

Yes I am, as the following playground snippet shows. Of course, my explanation may be wrong.

protocol Reusable {
    static var reusableIdentifier: String { get }
}

extension Reusable {
    static var reusableIdentifier: String {
        return String(Self)
    }
}

class Cell {
    required init() {}
}

class ParentView:Cell, Reusable {}
class ChildView: ParentView {}

let ri = ChildView.reusableIdentifier
print(ri) // prints "ChildView", as expected

class TableView {}

extension TableView {
    func dequeue<T: Cell where T: Reusable>() -> T {
        print(T.reusableIdentifier)

        return T()
    }
}

let tableView = TableView()

tableView.dequeue() as ChildView // prints ParentView for Self, ChildView for self

[AliSoftware]

Ok, talked to someone working on the Swift compiler and it appears that it's actually a bug

https://twitter.com/jckarter/status/691643221487693824

Not sure if the right solution is to use self though, probably is but before making that change I want to investigate more and especially ensure that it won't have side-effects. Like for some edge cases like when you customize the description or debugDescription of the class or the CustomMirror etc.

I definitely have to add Unit Tests to that pod anyway, might be a good occasion to do so.

[rollandjb]

That's interesting. And of course you are right, customising description and debugDescription could cause trouble! In the mean time it works for me where I derive cells from a base cell.

Furthermore, my explanation was inaccurate!

[AliSoftware]

Bug reported on the Swift bug tracker: https://bugs.swift.org/browse/SR-617

Will try to add unit tests and see how we could workaround this (using self maybe as you suggested, but have to confirm with tests it works in all conditions first) soon. (Don't hesitate to make a PR to add some Unit Tests too, especially test cases matching your use case and demonstrating the issue)

[AliSoftware]

Closed by 5cc715c