I did not know of this behavior, but it looks like if the superclasses
designated initializer is just a plain init() then it will automatically call
super.init() from your subclass.
There is no way to avoid not calling your superclasses’s designated initializer
and I guess the compiler ensures
The swift-commits archive is empty and I am no longer receiving email updates
when a commit is made.
Where is the best place to report or address this?
Thanks,
Brandon
___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman
I don’t understand why this is a problem
protocol Element {
}
enum ElementNode {
case element(T)
case empty
}
var childElements = [ElementNode]()
I need to represent an array of my nodes that could be multiple kinds of
elements
Is there a workaround?
Brandon_
t; Nevin
>
>
> On Wed, Dec 28, 2016 at 6:41 PM, Brandon Knope via swift-users
> mailto:swift-users@swift.org>> wrote:
> I don’t understand why this is a problem
>
> protocol Element {
>
> }
>
> enum ElementNode {
> case element(T)
> ca
I am at a loss:
Why does this not work:
class Test {
let timer: Timer!
init() {
timer = Timer.scheduledTimer(timeInterval: 20, target: self, selector:
#selector(test(_:)), userInfo: nil, repeats: true)
}
@objc func test(_ timer: Timer) {
}
}
error:
