These issues which you have raised have been discussed thoroughly on this list some time ago. It was distilled into a very well written proposal, SE-0018, that was evaluated and deferred. I would recommend that you and all people who are interested in this topic review the initial pitch and the subsequent discussions that took place.<br><br>At the conclusion of that process, any improvements for memberwise initialization were deemed out of scope for Swift 3. Subsequently, all sugar was out of scope for Swift 4 phase 1 and deemed to be extremely low priority for Swift 4 phase 2. Whether the topic will be in scope again is an open question.<br><br>The summary of the core team's decision is unusually long and extraordinarily enlightening. The issues about this feature being out of scope are discussed as "meta-points," and an extensive amount of text explains the thought process behind that conclusion. Beyond that, however, the decision also explores a truly remarkable set of possible solutions to the underlying issue, and it raises very interesting (non-meta) points that would have to be carefully considered before any revised proposal.<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 22, 2017 at 16:14 Mike Kluev 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"><div dir="ltr">On 22 June 2017 at 02:46, Jon Shier <span dir="ltr"><<a href="mailto:jon@jonshier.com" target="_blank">jon@jonshier.com</a>></span> wrote:</div><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div></div><div>1 can already be accomplished by moving the custom initializer into an extension. </div></div></blockquote><div><br></div></div></div></div></div><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div>it can indeed. although if you need to create an extension just for this purpose it feels like a workaround, takes more lines and is less obvious, imho. plus if #3 is accepted (the same construct for classes) it would be more consistent to have it in structs as well.</div></div></div></div></div><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Mike</div><div><br></div></div></div></div></div>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>