Re: [swift-evolution] [Pitch] Ban the top value in Int/UInt / use smaller Integer

2016-10-20 Thread Joe Groff via swift-evolution
> On Oct 20, 2016, at 8:25 AM, Haravikk via swift-evolution > wrote: > > >> On 20 Oct 2016, at 15:51, Martin Waitz via swift-evolution >> wrote: >> >> Hello, >> >>> It's just that a common data type wasting almost half the space seems

Re: [swift-evolution] [Pitch] Ban the top value in Int/UInt / use smaller Integer

2016-10-20 Thread Haravikk via swift-evolution
> On 20 Oct 2016, at 15:51, Martin Waitz via swift-evolution > wrote: > > Hello, > >> It's just that a common data type wasting almost half the space seems >> inefficient. I guess this is also the reason why they didn't adopt optional >> integers widely in stdlib.

Re: [swift-evolution] [Pitch] Ban the top value in Int/UInt / use smaller Integer

2016-10-20 Thread Martin Waitz via swift-evolution
Hello, It's just that a common data type wasting almost half the space seems inefficient. I guess this is also the reason why they didn't adopt optional integers widely in stdlib. When someone is really interested in fitting an optional integer into one machine word, then the best way would