<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><p>We added a note to the proposal:</p>
<ul>
<li>Both <code>Type<T></code> and <code>AnyType<T></code> will be declared in the Swift standard library even if part of the implementation might be compiler magic. That move is really important to allow developers to created custom <em>nested</em> types named as <code>Type</code>. <code>ModuleName.TypeName.Type</code> is ambigious today, but will become possible after this proposal. That means <code>Type<T></code> and <code>AnyType<T></code> will be shortcuts for <code>Swift.Type<T></code> and <code>Swift.AnyType<T></code>.</li>
</ul>
<p>We also think that the proposal is ready for the review. :)</p>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <br> <div id="bloop_sign_1487536878723518976" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 19. Februar 2017 um 09:40:19, Adrian Zubarev (<a href="mailto:adrian.zubarev@devandartist.com">adrian.zubarev@devandartist.com</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div></div><div>
<title></title>
<div class="bloop_markdown">
<p>Actually Brent has just now convinced me that
<code>Metatype</code> would be a bad name to choose. So forget what
I said in my last messages.</p>
</div>
<div class="bloop_original_html">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br></div>
<br>
<div id="bloop_sign_1487493530012287232" class="bloop_sign">
<div style="font-family:helvetica,arial;font-size:13px">
-- <br>
Adrian Zubarev<br>
Sent with Airmail</div>
</div>
<br>
<p class="airmail_on">Am 18. Februar 2017 um 17:55:33, Adrian
Zubarev (<a href="mailto:adrian.zubarev@devandartist.com">adrian.zubarev@devandartist.com</a>)
schrieb:</p>
<blockquote type="cite" class="clean_bq">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>
<div class="bloop_markdown">
<p><span>The problem I was describing is about nested types named
<code>.Type</code>, indeed. Assuming the proposal would go with
<code>Type<T></code>, then it means you _might_ be able to
create nested types called <code>Type</code>, but you always would
need to call if through the whole namespace (e.g.
<code>A.B.Type</code>). That is a huge downside.</span></p>
<p><span><code>Metatype</code> on the other hand describes exactly
what that _thing_ really is.</span></p>
<p><span>Currently on a different branch I added this important
note to the alternatives, but I’d rather use these types for the
whole proposal.</span></p>
<blockquote>
<p><span>Assuming that the accepted proposal decides to use
<strong><code>Metatype<T></code></strong>,
<strong><code>AnyMetatype<T></code></strong> over
<strong><code>Type<T></code></strong> and
<strong><code>AnyType<T></code></strong> would imply that the
type <code>Type</code> would no longer be ambiguous to use in
custome modules. However, such naming choice will affect the
<code>type(of:)</code> function. It <em>might</em> be necessary to
align the function name to <code>metatype(of:)</code> to avoid any
confusion, which will result in another breaking change.
Alternatively we could leave the function as <code>func
type<T>(of instance: T) ->
AnyMetatype<T></code>.</span></p>
</blockquote>
<p><span>If we’re going for breaking changes again than I’d prefer
to align the magical <code>type(of:)</code> function to
<code>metatype(of:)</code>.</span></p>
<p><span>I’d love to hear more input on this.</span></p>
</div>
<div class="bloop_original_html">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<span><br></span></div>
<span><br></span>
<div id="bloop_sign_1487436363898182912" class="bloop_sign">
<div style="font-family:helvetica,arial;font-size:13px">
<span>-- <br>
Adrian Zubarev<br>
Sent with Airmail</span></div>
</div>
<span><br></span>
<p class="airmail_on"><span>Am 18. Februar 2017 um 17:00:27, Anton
Zhilin (<a href="mailto:antonyzhilin@gmail.com">antonyzhilin@gmail.com</a>)
schrieb:</span></p>
<blockquote type="cite" class="clean_bq">
<div>
<div>
<div dir="ltr">
<div class="markdown-here-wrapper" style="">
<p style="margin:0px 0px 1.2em!important"><span><span><code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Type</code> is a bad name for a public type: <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
FooType</code> is almost always a better name. Libraries that
describe “just types”, Swift types, can as well use <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Metatype</code> or <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Mirror</code> or something.<br>
For nested types, like <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Foo.Type</code>, in the meaning of “type of <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Foo</code>“, <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Type</code> can’t be used even now.<br>
I’d give up on <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">
Type</code> name for the greater future of
metatypes.</span></span></p>
<p style="margin:0px 0px 1.2em!important"><span>2017-02-18 16:28
GMT+03:00 Adrian Zubarev <<a href="mailto:adrian.zubarev@devandartist.com" target="_blank">adrian.zubarev@devandartist.com</a>>:</span></p>
<p style="margin:0px 0px 1.2em!important"></p>
<div class="markdown-here-exclude">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div class="m_-3396370866651105684bloop_markdown">
<p><span>Personally I’d prefer <code>Metatype<T></code> and
<code>AnyMetatype<T></code> to get rid of the restriction
where you mostly cannot create custom types called
<code>Type</code>, which annoys me a lot. Sometimes
<code>Kind</code> as a good workaround but there are times where
<code>Kind</code> doesn’t fit. :/</span></p>
</div>
</div>
</blockquote>
</div>
<p style="margin:0px 0px 1.2em!important"></p>
<div title="MDH:YFR5cGVgIGlzIGEgYmFkIG5hbWUgZm9yIGEgcHVibGljIHR5cGU6IGBGb29UeXBlYCBpcyBhbG1v c3QgYWx3YXlzIGEgYmV0dGVyIG5hbWUuIExpYnJhcmllcyB0aGF0IGRlc2NyaWJlICJqdXN0IHR5 cGVzIiwgU3dpZnQgdHlwZXMsIGNhbiBhcyB3ZWxsIHVzZSBgTWV0YXR5cGVgIG9yIGBNaXJyb3Jg IG9yIHNvbWV0aGluZy48ZGl2PkZvciBuZXN0ZWQgdHlwZXMsIGxpa2UgYEZvby5UeXBlYCwgaW4g dGhlIG1lYW5pbmcgb2YgInR5cGUgb2YgYEZvb2AiLCBgVHlwZWAgY2FuJ3QgYmUgdXNlZCBldmVu IG5vdy48L2Rpdj48ZGl2PkknZCBnaXZlIHVwIG9uIGBUeXBlYCBuYW1lIGZvciB0aGUgZ3JlYXRl ciBmdXR1cmUgb2YgbWV0YXR5cGVzLjwvZGl2PjxkaXY+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEi Pjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+MjAxNy0wMi0xOCAxNjoyOCBHTVQrMDM6MDAg QWRyaWFuIFp1YmFyZXYgPHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86YWRyaWFu Lnp1YmFyZXZAZGV2YW5kYXJ0aXN0LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFkcmlhbi56dWJhcmV2 QGRldmFuZGFydGlzdC5jb208L2E+Jmd0Ozwvc3Bhbj46PGJyPjxibG9ja3F1b3RlIGNsYXNzPSJn bWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2Nj IHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPjxkaXYgc3R5bGU9IndvcmQtd3JhcDpicmVhay13b3Jk Ij48ZGl2IGNsYXNzPSJtXy0zMzk2MzcwODY2NjUxMTA1Njg0Ymxvb3BfbWFya2Rvd24iPjxwPlBl cnNvbmFsbHkgSeKAmWQgcHJlZmVyIDxjb2RlPk1ldGF0eXBlJmx0O1QmZ3Q7PC9jb2RlPiBhbmQg PGNvZGU+QW55TWV0YXR5cGUmbHQ7VCZndDs8L2NvZGU+IHRvIGdldCByaWQgb2YgdGhlIHJlc3Ry aWN0aW9uIHdoZXJlIHlvdSBtb3N0bHkgY2Fubm90IGNyZWF0ZSBjdXN0b20gdHlwZXMgY2FsbGVk IDxjb2RlPlR5cGU8L2NvZGU+LCB3aGljaCBhbm5veXMgbWUgYSBsb3QuIFNvbWV0aW1lcyA8Y29k ZT5LaW5kPC9jb2RlPiBhcyBhIGdvb2Qgd29ya2Fyb3VuZCBidXQgdGhlcmUgYXJlIHRpbWVzIHdo ZXJlIDxjb2RlPktpbmQ8L2NvZGU+IGRvZXNu4oCZdCBmaXQuIDovPC9wPjwvZGl2PjwvZGl2Pjwv YmxvY2txdW90ZT48L2Rpdj48L2Rpdj48L2Rpdj4=" style="height:0;width:0;max-height:0;max-width:0;overflow:hidden;font-size:0em;padding:0;margin:0">
<span></span></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div class="bloop_markdown"></div>
</div>
</div>
</blockquote>
</div>
<div class="bloop_markdown"></div>
</div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>