<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="">Le 11 sept. 2017 à 23:37, Tony Allevato via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_quote"><div class="">All this is a subtle, but important, distinction. One day, when Swift has the ability to introspect metadata about a type and its properties, someone may want to use a hypothetical "transient" attribute for something wholly unrelated to synthesis.</div></div></div></div></blockquote><br class=""></div><div>My thoughts exactly. The language is not ready yet for exclusion of some members in synthetic code.</div><div><br class=""></div><div>Gwendal</div><br class=""></body></html>