<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 22 Jul 2016, at 01:41, Xiaodi Wu 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=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: 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; float: none; display: inline !important;" class="">1. A consolidated section--which can be on the brief side--on the current art (i.e., how do things currently work?). Some information is already present, but the prose is not possible to follow unless one is already an expert in the area. Please start each paragraph with a topic sentence leading into an explanation in English, not just code, of the current behavior. Perhaps you could used (attributed) quotations from existing Swift documentation if necessary.</span></div></blockquote></div><br class=""><div class="">I specifically agree with this point. I regard myself as a knowledgable Swift developer, but metatypes have always been a bit fuzzy for me, which refrained me from commenting on the proposal. If instead, the proposal tried to explain as succinctly as possible the current situation and its defects, I’m sure I’d have a higher chance of understand the problem at hand and commenting on it.</div></body></html>