You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually when you use hex notation for numbers, you are trying to create an unsigned value with a particular bit pattern. To facilitate that, it has been proposed that 0x hex integer literals represent unsigned integers of size determined by the number of digits:
hex literals with 1-2 digits create Uint8 values
hex literals with 3-4 digits create Uint16 values
hex literals with 5-8 digits create Uint32 values
hex literals with 9-16 digits create Uint64 values
This proposal would make leading zeros meaningful for hex literals, but only in that they affect the storage size of the resulting value, never its numeric value, which seems acceptable and intuitive.
The text was updated successfully, but these errors were encountered:
* 'master' of github.com:JuliaLang/julia:
closing issue #197, hex literals give unsigned ints sized by digits
storing ASTs serialized to save memory part of issue #261 significantly cuts the number of live objects, making GC much faster
Usually when you use hex notation for numbers, you are trying to create an unsigned value with a particular bit pattern. To facilitate that, it has been proposed that
0x
hex integer literals represent unsigned integers of size determined by the number of digits:Uint8
valuesUint16
valuesUint32
valuesUint64
valuesThis proposal would make leading zeros meaningful for hex literals, but only in that they affect the storage size of the resulting value, never its numeric value, which seems acceptable and intuitive.
The text was updated successfully, but these errors were encountered: