Swift 1.2: 'self' used before super.init call -


i have code:

class someviewcontroller : uiviewcontroller {   let deferred : ()->()   required init(coder adecoder : nscoder) {     deferred = {         self.dosomething()     }      super.init(coder: adecoder)  }   func dosomething() {     // things....  }  }

in swift 1.2 fails compile error:

'self' used before super.init call

in pre-1.2 days, can address in number of ways such implicitly unwrapped conditionals. approach won't work longer.

i've seen other answers reference 2-stage initialization or lazy decorator, both sacrifice immutability of property. surely must solvable in swift 1.2, i'm out of ideas.

here's interim workaround:

private(set) var deferred : ()->() = { }  required init(coder adecoder : nscoder) {     super.init(coder: adecoder)     self.deferred = {         self.dosomething()     }  }

my thinking is, okay, did "sacrifice immutability of property", public perspective property remains immutable because setter private.


-

Popular posts from this blog

debugging - Reference - What does this error mean in PHP? -

what this? this number of answers warnings, errors , notices might encounter while programming php , have no clue how fix. community wiki, invited participate in adding , maintaining list. why this? questions "headers sent" or "calling member of non-object" pop on stack overflow. root cause of questions same. answers questions typically repeat them , show op line change in his/her particular case. these answers not add value site because apply op's particular code. other users having same error can not read solution out of because localized. sad, because once understood root cause, fixing error trivial. hence, list tries explain solution in general way apply. what should here? if question has been marked duplicate of this, please find error message below , apply fix code. answers contain further links investigate in case shouldn't clear general answer alone. if want contribute, please add "favorite" error message, warning or notic...
Read more

c++ - Why doesn't unordered_set provide an array access operator -

i'm curious why stl container unordered_set , has constant time complexity random access on average, not provide method accessing elements distance first element in container. example: t& unordered_set::operator[](size_t index) { return *(begin() + index); } accessing element "by distance" implies there meaningful way measure distance. trouble std::unordered_set is is, well, unordered . hence, there no meaningful way of explaining "some distance beginning" in non-arbitrary way. if want access distance, copy data vector: std::vector tmp(unordered.begin(), unordered.end());
Read more