Add typed array literals and numeric hex literals - #194
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #159
Introduce explicit types for array literals and redefine hexadecimal literals as numerals. Byte sequences now require explicit casts, while
pubkey,sig, anddatasigaccept correctlysized hex literals directly.
Language Behavior Changes
T{...}instead of untyped[...]syntax.T[]{...}produces a dynamic array,T[_]{...}infers a fixed size, andT[N]{...}requires exactlyNelements.Nested elements must have compatible types and equal fixed dimensions.
They no longer implicitly produce byte arrays. Raw bytes require an immediate byte-array cast:
Hex literals longer than eight bytes remain invalid unless immediately cast to a byte array or fixed byte-sequence type.