<div dir="ltr">On Sun, Jan 29, 2017 at 2:03 PM, David Sweeris <span dir="ltr"><<a href="mailto:davesweeris@mac.com" target="_blank">davesweeris@mac.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="auto"><span class="gmail-"><div><br></div><div>On Jan 29, 2017, at 10:36, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>> wrote:<br><br></div><blockquote type="cite">Hmm, interesting. I might be tempted to use a 40-bit type for large arrays, but the performance hit for any useful computation over a large array would probably tilt heavily in favor of plain 64-bit integers. What's your use case for such a 40-bit type? And is it common enough to justify such a facility in the stdlib vs. providing the tools to build it yourself?<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
</blockquote></div>
</blockquote><div><br></div></span>I can think of two use-cases. One — saving memory for large #s of allocations — you already mentioned. The other is for easing interactions with on-disk data. For example, if you're working with some format that has 24-bit ints, you could use "CompoundWhateverItWasCalled<<wbr>Int8,Int16>". It doesn't make much difference when you're loading the data, but when you're writing it back out, you wouldn't have to worry about trimming that last byte or what to do if the value won't fit in 24 bits. I mean, obviously you'd still have to handle it, but the overflow would happen in the calculation that causes it rather then while you're busy doing something else.<br><div><br></div><div>In terms of justification, I think probably all I can offer is that I <i>think</i> it wouldn't be materially harder or less efficient to implement this than it would be to write a "DoubleWidth<T>" type... It's extra functionality for free, at least in terms of effort. It would increase the API surface, but not by much. Assuming that "DoubleWidth" could just be a typealias, that is. If I'm wrong about it being "that easy", then I don't think it'd be worth it. As you noted, it is somewhat niche.</div></div></blockquote><div><br></div><div>Unless I'm mistaken, DoubleWidth would be implemented using doubleWidthMultiply and doubleWidthDivide facilities provided in these new integer protocols. As the protocol documentation says, DoubleWidth is really intended for wider types, not arbitrarily sized narrower ones. There's no obvious way I can see to implement the same thing for two types of unequal bit width, short of determining dynamically, at each operation, which of your two types has the larger bit width and truncating bits accordingly. So if you want a 24-bit Int, it's unclear to me why you'd choose what's effectively DoubleWidth<Int16> minus 8 bits rather than Int32 minus 8 bits.</div><div><br></div></div></div></div>