Hex and string built-ins #134
Draft
Conversation
This file contains 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
… "push label" ops
… remains correct over time.
…is messy and there are several hacks I need to remove. Also I should write a more rusty code.
…the code should be optimized, but the general idea seems to work.
…ressing some of the changes proposed by Sam.
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.
This PR implements the two built-ins mentioned in issue #106 (%hex(...) & %string(...)). Since it's based on the reimplementation of the backend introduced in PR #133, I'm keeping this PR as a draft until #133 is merged.
The built-in %string(...) puts the full string into the bytecode without regard to length. Please let me know if you want to use a different layout.