<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=""><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="">We don’t want to add conformance then find out that was a mistake.</div></div></div></blockquote><div>I think we also don't want to create restrictions based on future additions that might never happen...</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div 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="">Besides that they can’t be Sequences, unless you throw away allowing parallel/vector processing in the future. (That can’t be bolted onto Version 2, since committing to Sequence means you committed to single-thread iteration.)</div></div></div></blockquote></div>… especially as I doubt that those restrictions are required at all:<div class="">As I said, just conforming to collection doesn't forbid to add things that aren't in the protocol.</div><div class="">Why should it be impossible to add vector processing support when it is decided that this feature should be added to the language?</div><div class=""><br class=""></div><div class="">Parallel processing would be nice for Array<T> as well — and I can't think of someone really arguing to remove conformance to Sequence from Array now…</div><div class=""><br class=""></div><div class="">The situation is very different with Array<T, size: Int>:</div><div class="">If it is decided to add generic value parameters* to Swift, it imho would be awkward not to utilise this powerful for fixed-size arrays, and all those syntax-additions that are discussed for them would become very questionable at least.</div><div class=""><br class=""></div><div class="">Tino</div><div class="">Which imho definitely should happen: Whereas many additions to Swift are more a less a question of personal preference, generic value parameters offer protection from some kinds of bugs whose severity can actually be proven with real-word examples that had terrible consequences.</div><div class=""><br class=""></div></body></html>