Account for LangError #31
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
✅ Deploy Preview for squink-splash canceled.
|
DoubleOTheven
approved these changes
Jan 4, 2023
|
linking use-ink/ink#1512 |
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.
The new ink! beta wraps cross contract calls into a
Result<T, LangError>. Our low level cross contract call didn't account for that and hence failed to decode theTurn. It just decoded garbage which then turned out to be out of bounds.@xermicus You need to make sure that your handwritten sol contract wraps the value as to game expects this after this PR is merged.
Optionjust prepends one byte (0=None, 1=Some).