This repository has been archived by the owner on Dec 12, 2024. It is now read-only.
feat: Struct & Message declaration syntax + Optionals #95
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
Merged
novusnota
force-pushed
the
6+26-message-and-serialization
branch
from
bc78184 to
48ba7e0
Compare
novusnota
force-pushed
the
6+26-message-and-serialization
branch
from
48ba7e0 to
abc80b2
Compare
|
Ready for review |
…s/tact-docs into 6+26-message-and-serialization
added motivation to use custom numeric ids to match opcodes
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Significantly modified the first page of the Book (about types), and added a "Defining composite types" page, which describes:
?) with the showcase of a!!operatorAdditionally, first page now makes a small reference to the new and non-existing yet page about Ints — it would be added today in a separate PR.
Closes #6.
As stated there #6 (comment), details on
remainingkeyword as well asbytes64andbytes32ones in TL-B serialization would be covered in a different PR, which would target #26 and tact-lang/tact#1178, and an update in/book/funcpage.