A series of improvements to Tact Language

[Gusarich]

Summary

Implement necessary improvements and features in Tact language used for writing TON smart contracts

Bounty Context

Why it's Important?
Tact language is the core for writing smart contracts in TON. This being the case, improving its functionality, user-friendliness, and the implementation of new features is crucial in ensuring the efficiency and user experience of contract creation in TON Blockchain.

Problem showcase
Currently, Tact language for TON is quite young in its development stage. There are a multitude of things that need implementation, fixing and improvement.

Potential Solution
The solution involves working on multiple pull requests with new features and improvements for Tact language. The pull requests will be based on the listed items from the public roadmap for the development of Tact language. By systematically implementing these requested changes, we can significantly enhance Tact language readiness for production and user-friendliness.

To-do list

• Augmented assignment operators tact-lang/tact#87
• add .del function to maps tact-lang/tact#95
• add ubuntu & windows & macos CI tact-lang/tact#96
• Add conditional expressions tact-lang/tact#97
• Add bin and oct integer literals & Allow underscores in them tact-lang/tact#99
• Slices and Strings comparisons tact-lang/tact#105
• Add native map traversing functionality tact-lang/tact#106
• Refactor CI workflow and add tact-template testing tact-lang/tact#111

This list may be filled with more features based on feedback from developers

References

• Tact Language roadmap

REWARD

• SBT Bounty Reward
• 3000 USD in TON

🪄 Created with the help of TON Bounties Creator Bot.

[Gusarich]

@delovoyhomie please assign me to this issue 🙂

[delovoyhomie]

@anton-trunov, let's decide a reward for this bounty!

[Gusarich]

@delovoyhomie I think something around 2-3k USD will be fair reward for this bounty.

[anton-trunov]

I think USD 3k is definitely fair for this amount of work

[delovoyhomie]

LGTM!

[howardpen9]

Go og go

[Sashka231]

Summary

Implement necessary improvements and features in Tact language used for writing TON smart contracts

Bounty Context

Why it's Important? Tact language is the core for writing smart contracts in TON. This being the case, improving its functionality, user-friendliness, and the implementation of new features is crucial in ensuring the efficiency and user experience of contract creation in TON Blockchain.

Problem showcase Currently, Tact language for TON is quite young in its development stage. There are a multitude of things that need implementation, fixing and improvement.

Potential Solution The solution involves working on multiple pull requests with new features and improvements for Tact language. The pull requests will be based on the listed items from the public roadmap for the development of Tact language. By systematically implementing these requested changes, we can significantly enhance Tact language readiness for production and user-friendliness.

To-do list

• Augmented assignment operators tact-lang/tact#87
• add .del function to maps tact-lang/tact#95
• add ubuntu & windows & macos CI tact-lang/tact#96
• Add conditional expressions tact-lang/tact#97
• Add bin and oct integer literals & Allow underscores in them tact-lang/tact#99
• Slices and Strings comparisons tact-lang/tact#105
• Add native map traversing functionality tact-lang/tact#106
• Refactor CI workflow and add tact-template testing tact-lang/tact#111
• Generic for loop tact-lang/tact#168
• Tact lacks support of exotic cells tact-lang/tact#154

This list may be filled with more features based on feedback from developers

References

• Tact Language roadmap

REWARD

• SBT Bounty Reward
• 3000 USD in TON

🪄 Created with the help of TON Bounties Creator Bot.

[anton-trunov]

@delovoyhomie looks like this has been done already :) green light from the Tact team side

[delovoyhomie]

@Gusarich thank you for the contribution!

To accurately recognize your valuable contributions in our repository, we kindly request you to submit a Pull Request to the Hall of Fame file, providing the wallet address and a link to the bounty with the number.

Please follow these steps:

1. Fork the repository (if you haven't already).

2. Edit the Hall of Fame file, commit, and push your changes.

3. Create a Pull Request from your fork to the main repository, providing the wallet address and a link to the bounty with the number (for example, Pull Request Article: Generation of block random seed #136).
   For reference on what your entry should look like, please see the examples of past merged pull requests.

4. And please follow the questbook proposal stage in accordance with the bounty guideline