Skip to content

correct 0x literal info #47348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StefanKarpinski merged 2 commits into from
Oct 28, 2022
Merged

correct 0x literal info #47348

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
25d5283
correct 0x literal info
udohjeremiah Oct 27, 2022
bf85bcb
Update doc/src/manual/integers-and-floating-point-numbers.md
StefanKarpinski Oct 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion doc/src/manual/integers-and-floating-point-numbers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,9 @@ determining storage size of a literal. So `0x01` is a `UInt8` while `0x0001` is

That allows the user to control the size.

Values which cannot be stored in `UInt128` cannot be written as such literals.
Unsigned literals (starting with `0x`) that encode integers too large to be represented as
`UInt128` values will construct `BigInt` values instead. This is not an unsigned type but
it is the only built-in type big enough to represent such large integer values.

Binary, octal, and hexadecimal literals may be signed by a `-` immediately preceding the
unsigned literal. They produce an unsigned integer of the same size as the unsigned literal
Expand Down