Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(docs): compilation report #1309

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

feat(docs): compilation report #1309

wants to merge 5 commits into from

Conversation

novusnota
Copy link
Member

Also adjusted the generated report itself, just so it's a valid and readable markdown.

Issue

Closes #1094.
Towards #1136 (created the page).

Checklist

  • I have updated CHANGELOG.md
  • I have run the linter, formatter and spellchecker
  • I did not do unrelated and/or undiscussed refactorings

@novusnota novusnota added this to the Doc: 2025-01 milestone Jan 14, 2025
@novusnota novusnota requested a review from a team as a code owner January 14, 2025 04:14
@anton-trunov anton-trunov self-assigned this Jan 14, 2025
docs/src/content/docs/book/compile.mdx Outdated Show resolved Hide resolved
docs/src/content/docs/book/compile.mdx Outdated Show resolved Hide resolved
Comment on lines +59 to +69
[TL-B schema][tlb] of each [Message][message] contains its opcode, which is handy for looking up the auto-generated opcodes as well as confirming the [manually provided ones](/book/structs-and-messages#message-opcodes). For example:

```md
### Deploy
TL-B: `deploy#946a98b6 queryId:uint64 = Deploy`
Signature: `Deploy{queryId:uint64}`

### Seven
TL-B: `seven#00000007 = Seven`
Signature: `Seven{}`
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's

  • make it a subsection with its own link
  • link the subsection from the messages page
  • be more explicit, i.e. provide the corresponding Tact message declarations to their respective TL-B schemes
  • explicitly say 0x946a98b6 and 0x00000007 are the opcodes
  • mention that the opcodes are in hex as it is important for something like foobar#94609816


There, the `lshift(){:tact}` getter has a single argument `x`, whereas the `gas(){:tact}` getter has no arguments.

#### Exit codes {#exit-codes}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should link this subsection from the exit codes page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a description of compilation report produced by the compiler
2 participants