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
I was surprised to discover today that Cryptol lets you write tuple selectors in hexadecimal:
Cryptol> (True, True).0x1 True Cryptol> { x | 0x1 = True } where x = (False, False) (False, True)
This works similarly for octal and binary.
Is this intentional? We should either document this, or disallow it.
The text was updated successfully, but these errors were encountered:
Selector should be just in base 10. Since I am reworking them to work around the interactions with fractional literals I'll fix that too
Sorry, something went wrong.
5d04936
yav
No branches or pull requests
I was surprised to discover today that Cryptol lets you write tuple selectors in hexadecimal:
This works similarly for octal and binary.
Is this intentional? We should either document this, or disallow it.
The text was updated successfully, but these errors were encountered: