<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Why would you have an immutable instance member that is always going to have a constant value of 1? That just wastes space by duplicating the constant value in many instances. However it is quite reasonable to have an immutable instance member that<span class="Apple-converted-space"> </span><b class="">defaults<span class="Apple-converted-space"> </span></b>to 1, but may have a different value depending on the initializer that is used for the instance.</div></div></blockquote></div>All true:<div class="">"let n = 1" is useless, and it would be useful to take this as a hint for the generated initializer… but it would break the rules for let.</div><div class=""><br class=""></div><div class="">Afair, in an older version of Swift, you could change the value of constants in init (I think it was changed when delayed assignment for constants was introduced).</div><div class="">Is this false memory, or does anyone know about the motivation for that change?</div></body></html>