<div dir="ltr"><div>@Félix,</div><div><br></div>For the first point, the issue you talked about isn't new. We can enter into that mess easily right now just by changing `let` to `var`.<div><br></div><div>For the second point, well.. I agree with you and @Michel, thank you guys. It do make sense, I should've noticed it earlier. This is not an appropriate solution to make the current "didSet" keyword available for `let` property. </div><div><br></div><div>But I'm still thinking it should not be a problem at all if we add something new, such as "didInit", which only get called for the very first time when property is assigned a value.</div><div><br></div><div>What do you think?</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 23, 2015 at 7:39 PM, Michel Fortin <span dir="ltr"><<a href="mailto:michel.fortin@michelf.ca" target="_blank">michel.fortin@michelf.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Le 23 déc. 2015 à 11:07, Félix Cloutier via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> a écrit :<br>
<br>
> willSet and didSet are currently not even called from the init method.<br>
<br>
</span>And they can't, because in those two blocks you have access to the old value as well as the new value. How would that work when you're setting the initial value?<br>
<br>
var value: Int {<br>
willSet { print("willSet \(value) -> \(newValue)") }<br>
didSet { print("didSet \(oldValue) -> \(value)") }<br>
}<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Michel Fortin<br>
<a href="https://michelf.ca" rel="noreferrer" target="_blank">https://michelf.ca</a><br>
<br>
</font></span></blockquote></div><br></div>