<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPad</div><div><br>On Jun 30, 2016, at 6:59 PM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 30, 2016, at 5:47 PM, James Berry <<a href="mailto:jberry@rogueorbit.com" class="">jberry@rogueorbit.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" style="font-family: Palatino-Roman; 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;" class=""><br class="Apple-interchange-newline">On Jun 30, 2016, at 4:05 PM, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">on Thu Jun 30 2016, Erica Sadun <<a href="http://erica-at-ericasadun.com" class="">erica-AT-ericasadun.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">On Jun 30, 2016, at 4:41 PM, Dave Abrahams <<a href="mailto:dabrahams@apple.com" class="">dabrahams@apple.com</a>> wrote:<br class=""><blockquote type="cite" class="">I mentioned this in a comment on the gist already, but I'm really not<br class="">digging the "array" in `arraySpacing`. We've already moved from top-level<br class="">"stride" to "memory layout spacing," gaining plenty of clarity. I'm<br class="">skeptical that the "array" adds anything more. Moreover, it muddies the<br class="">waters by mentioning a specific type (Array) in a context where you're<br class="">querying the memory layout properties of another type.<br class=""></blockquote><br class="">OK, I agree with that. If we have “alignment” rather than<br class="">“defaultAlignment,” I suppose we can have plain “spacing.”<br class=""></blockquote><br class="">No way to last-second sell you on interval rather than spacing?<br class=""></blockquote><br class="">If you can explain why it's better.<br class=""><br class=""><blockquote type="cite" class="">// Returns the least possible interval between distinct instances of<br class="">/// `T` in memory. The result is always positive.<br class=""></blockquote><br class="">For me, “interval” doesn't go with “size” and “alignment,” which are all<br class="">about physical distances and locations. There are all kinds of<br class="">“intervals,” e.g. time intervals.<br class=""></blockquote><br style="font-family: Palatino-Roman; 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;" class=""><span style="font-family: Palatino-Roman; 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="">Hmm. Sounds like stride to me. stride or byteStride?</span><br style="font-family: Palatino-Roman; 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;" class=""><br style="font-family: Palatino-Roman; 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;" class=""><span style="font-family: Palatino-Roman; 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="">James</span></div></blockquote></div><br class=""><div class="">FAQ: "Why aren't you using the obvious phrase `stride` for something that clearly </div><div class="">returns the memory stride?"</div><div class=""><br class=""></div><div class="">ANSWER: "As stride already has a well-established meaning in the standard library,</div><div class="">this proposal changes the name to spacing, providing a simple but correct name that</div><div class="">works well enough in its intended use. Measuring memory is sufficiently esoteric</div><div class="">that we prefer to reserve `stride` for a more common use case."</div></div></blockquote><div><br></div><div>Counter: some words have more than one well established meaning when used in different contexts. 'spacing' isn't too bad here (much better than 'arraySpacing') but sticking to the term of art 'stride' would be best IMO. As James mentioned, spacing implies empty space *between* items whereas stride matches the meaning of this property *exactly* (which is why it is the term of art).</div><div><br></div><div>If a programmer can't distinguish between a 'stride' property on MemoryLayout and the 'stride' function they probably have no business doing anything which requires use of MemoryLayout in the first place.</div><br><blockquote type="cite"><div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>