Code that runs with integer overflow checking with 1 “jo” instruction can adopt full pointer-encoded bigint support with just 3 more instructions and 3 fewer integer bits. I wish safe sandboxed garbage collected languages did this by default.
Use the upper bits of the integer to say whether it’s a small int or a pointer to a big int. If it’s a big int, ops have to allocate them on the heap, so some scheme is needed to track and free them. If refcounting, then all int creation/destruction is costly.
-
-
I know (as I tried to say with "the garbage collected angle is clear") -- what's not obvious is why the language being safe and/or sandboxed is also relevant
-
Maybe it's not
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.