Enhance the Tact language for TON smart contracts with a focus on string handling.
Context
Why it's Important: Inscription is crucial when developing projects that require handling string messages. This library aims to minimize the time developers spend building with Tact by streamlining string handling.
Problem Showcase: Currently, when a string input is passed to a contract's receiver function, it cannot be directly used for numbers or addresses. For example, inputs like "1235" or a TON address in string form ("EQ...qe") require conversion to a buffer or slice. Then, it's necessary to calculate in 8-bit increments to convert these to hexadecimal values.
Potential Solution: Develop extended functions that can be easily integrated into contracts, allowing for direct use. These functions will enable developers to efficiently manage string inputs without the need for complex conversions.
Summary
Enhance the Tact language for TON smart contracts with a focus on string handling.
Context
Why it's Important: Inscription is crucial when developing projects that require handling string messages. This library aims to minimize the time developers spend building with Tact by streamlining string handling.
Problem Showcase: Currently, when a string input is passed to a contract's receiver function, it cannot be directly used for numbers or addresses. For example, inputs like "1235" or a TON address in string form ("EQ...qe") require conversion to a buffer or slice. Then, it's necessary to calculate in 8-bit increments to convert these to hexadecimal values.
Potential Solution: Develop extended functions that can be easily integrated into contracts, allowing for direct use. These functions will enable developers to efficiently manage string inputs without the need for complex conversions.
References
(Will Upload the Link later)
Estimate suggested reward