Use protocols <br><br>{get}<br>Can be used for let<br><br>{get set} <br>Can be used for var<br><div class="gmail_quote"><div dir="ltr">On Thu, Dec 15, 2016 at 1:16 AM Benjamin Spratling via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Howdy,<br class="gmail_msg">
Thanks, I’ll consider this as an alternative.<br class="gmail_msg">
I don’t see that this solves the issues of whether a property on a class is let, however.<br class="gmail_msg">
-Ben<br class="gmail_msg">
<br class="gmail_msg">
> On Dec 14, 2016, at 11:41 PM, Derrick Ho <<a href="mailto:wh1pch81n@gmail.com" class="gmail_msg" target="_blank">wh1pch81n@gmail.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> You might be able to ensure access modifiers by using protocols.<br class="gmail_msg">
><br class="gmail_msg">
> If you want to ensure that a class has a property called foo that is private you can make a private protocol that specifies a private property called foo.<br class="gmail_msg">
><br class="gmail_msg">
> This isn't a XCTest but it is a compile time check. If a programmer tries to change a private property to public then the the compiler will complain.<br class="gmail_msg">
><br class="gmail_msg">
> The same can be done with final. Make a protocol with a static method.<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>