Add ability to specify TEAL version #45
Merged
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
jasonpaulos
force-pushed
the
version-programs
branch
from
733247a to
2c256c2
Compare
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.
Add an optional version parameter to the
compileTealmethod. By defaultcompileTealwill compile expressions to TEAL v2. Once TEAL 3 support is added, users will need to pass in 3 to be able to take advantage of its new features.It's important for smart contract developers to know exactly which version of TEAL they are writing their contracts for, since some versions introduce new fields that must be checked to maintain a secure app. An example of this is version 2 of TEAL introducing the ability for transactions to rekey accounts.
Closes #31.