3 ms·
If this will see the light of day, I expect that iOS will have it first. Reasons? Apple controls its own CPUs, and Swift's 'normal' operators trap on overflow.
by Someone 11y ago
If this will see the light of day, I expect that iOS will have it first. Reasons? Apple controls its own CPUs, and Swift's 'normal' operators trap on overflow.
I also think that hardware support for tagged pointers (https://en.m.wikipedia.org/wiki/Tagged_pointer#Examples https://en.m.wikipedia.org/wiki/Tagged_pointer#Examples) may be worthwhile for iOS, but that need may decrease if ther will be a gradual move from Onjective-C to Swift.