<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On 03 Feb 2016, at 22:02, Jessy Catterwaul via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I do not agree about the implication. A property can be gotten, set, or both, in at least C#, where I used a ton of set-only properties.</div></div></div></blockquote><div><br class=""></div><div>Well, in C# it’s possible, sure, but it’s considered bad practice (see for example <a href="https://msdn.microsoft.com/en-us/library/ms182165.aspx" class="">https://msdn.microsoft.com/en-us/library/ms182165.aspx</a>), and I wouldn’t want it for Swift. Being a property implies it’s “variable-like” at least to some extent.</div><div><br class=""></div><div>~Sune</div><div><br class=""></div></div></body></html>