We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Also note that now that PowerShell/PowerShell#7993 has been merged, binary literals will need to be mentioned as well.
0b1011011 -> 91
This is related to issue #2965.
The text was updated successfully, but these errors were encountered:
@sdwheeler it will also need to be noted that that PR also introduced N suffix for native BigInteger, which works like the other type suffixes:
N
PS> [bigint]1000000000000000000000000000000 1000000000000000019884624838656 PS> [bigint]"1000000000000000000000000000000" 1000000000000000000000000000000 PS> 1000000000000000000000000000000n 1000000000000000000000000000000 PS> 1000000000000000000000000000000n -is [bigint] True
This alleviates the problem mentioned in the docs introduced in #2965. 😄
Sorry, something went wrong.
@vexx32 Thanks. Good to know.
Fix #4143 - add binary and bigint formats (#4159)
959c954
* Fix #4143 - add binary and bigint formats * review feedback * clarify hex literal length
952a47a
sdwheeler
No branches or pull requests
Issue Details
Also note that now that PowerShell/PowerShell#7993 has been merged, binary literals will need to be mentioned as well.
0b1011011 -> 91
This is related to issue #2965.
Version(s) of document impacted
Reason(s) for not selecting all version of documents
The text was updated successfully, but these errors were encountered: