Skip to content
This repository was archived by the owner on Dec 12, 2024. It is now read-only.

Conversation

@novusnota
Copy link
Member

@novusnota novusnota commented Apr 1, 2024

  • Enhanced each description
  • Added usage examples
  • Fixed links and added new ones

Closes #125 (single link by the end of dump() reference description)
Closes #112 (added allowed types for dump() function)
Closes #162 (document a built-in address function)

* Enhanced each description
* Added usage examples
* Fixed links and added new ones
* Added allowed types for `dump()` function
@novusnota novusnota requested a review from anton-trunov April 1, 2024 08:28
Copy link
Member

@anton-trunov anton-trunov left a comment

Choose a reason for hiding this comment

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

Awesome stuff!
I added a few questions that I thought might occur if I were a novice Tact programmer.

Co-authored-by: Anton Trunov <anton.a.trunov@gmail.com>
* context().sender vs. sender()
* links to TON Docs where suitable
* links to exit codes, where they're set
* other, smaller enhancements
@novusnota
Copy link
Member Author

  • context().sender vs. sender()
  • links to TON Docs where suitable
  • links to exit codes, where they're set
  • other, smaller enhancements

Also, documented a built-in compile-time address() function while we're at it.

@novusnota novusnota requested a review from anton-trunov April 7, 2024 18:55
@anton-trunov anton-trunov merged commit 0e429e4 into tact-lang:main Apr 8, 2024
@novusnota novusnota deleted the dump-types branch April 8, 2024 05:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document address builtin function Link dump reference to the debugging chapter Document allowed types for dump() function

2 participants