<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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 Jun 1, 2016, at 11:10 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Thu, Jun 2, 2016 at 12:03 AM, Jacob Bandes-Storch <span dir="ltr" class=""><<a href="mailto:jtbandes@gmail.com" target="_blank" class="">jtbandes@gmail.com</a>></span> wrote:<br class=""><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="ltr" class="">If it's worth continuing the discussion in this thread, I rather like the MemoryLayout<T>.size idea. For discoverability, we might want to have @availability(*, unavailable, message: "use MemoryLayout<T>.size, etc.") public init(){}.</div></blockquote><div class=""><br class=""></div><div class="">It's a nice syntax, but I'm not fully comfortable with the suggestion that sizeofValue(), etc. should go. Also, I wonder about the static vs. dynamic type issue here (despite having started the last thread, I still haven't sat down to think it through).</div><div class=""><br class=""></div></div></div></div>
</div></blockquote></div><br class=""><div class="">Updated with all the feedback so far. Will keep an eye on this.</div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div></body></html>