npx tact-fmt or by invoking a format command in your editor. You'd need to install the Tact's language server or the VSCode extension for that — see the tact-language-server repo for details.TactExitCodeNullReferenceException (128) and many others.sendRawMessage and sendRawMessageReturnForwardFee functions as replacements for their deprecated counterparts.sha256() function to about ~270 less gas used per call and added the keccak256() function that works with arbitrarily long slices.require() function now supports constants as its second parameter. You no longer need to provide identical string literals everywhere — define a string constant somewhere and reuse it!llms.txt, llms-full.txt and llms-small.txt files for you to use with your AIs. The small version is particularly interesting as it fits in the 200k context.BasechainAddress struct and related functions.npx tact-fmt in your projects — it supports checking the formatting via the --check flag, applying fixes via the --write flag, and can check both individual files and directories of files.
hash_norm field added to the Message structure. If the field is not present, it means this message not an external message, or the normalized hash_norm is equal to the regular hash.msg_hash parameter search also by normalized hash.api/v2/sendBocReturnHash returns the normalized hash in addition to the normal hash.
?: now correctly works with structs and null valuesget attribute is now correctly showndump() function with an argument of the unsupported StringBuilder type, the error will always be shown even if the debug mode is disabled&&= and ||= augmented assignment operators are now properly short-circuitedStruct.fromSlice(), Message.fromSlice(), and similar functions now work properly if the slice has been parsed entirely and the last field of the struct had the serialization annotation as remaining_ is prohibited for struct and message struct fields, function names, contract, and trait namesreturn statements in the receiver functionscontext().sender, it now calls the sender() function instead to optimize the gas usageinternalExternalReceiversOutsideMethodsMap option and its respective receiver order optimization were reworked to ensure compatibility with explorers and user walletsSendPayGasSeparately constant was deprecated in favor of SendPayFwdFeesSeparately — they're functionally identical, but the latter better expresses the intent and action that this optional flag makes when sending messagesStoppable trait now throws the exit code 133 instead of the exit code generated by the require() function from the "Contract stopped" messageexternal-in) on the TON blockchain was challenging for all of us due to minor metadata differences.
npx tact-fmt or by invoking a format command in your editor. You'd need to install the Tact's language server or the VSCode extension for that — see the tact-language-server repo for details.TactExitCodeNullReferenceException (128) and many others.sendRawMessage and sendRawMessageReturnForwardFee functions as replacements for their deprecated counterparts.sha256() function to about ~270 less gas used per call and added the keccak256() function that works with arbitrarily long slices.require() function now supports constants as its second parameter. You no longer need to provide identical string literals everywhere — define a string constant somewhere and reuse it!llms.txt, llms-full.txt and llms-small.txt files for you to use with your AIs. The small version is particularly interesting as it fits in the 200k context.BasechainAddress struct and related functions.npx tact-fmt in your projects — it supports checking the formatting via the --check flag, applying fixes via the --write flag, and can check both individual files and directories of files.type NewName = T1 | T2 | ...is and !isT? are now formally T | null. T1 | T2 will be directly mapped to TL-B (Either T1 T2). (Either SmallPayload LargePayload) becomesT1 | T2 | ... is a typed way to describe multiple constructors from TL/B. Generally, they can be used anywhere inside a storage or a message. hash_norm field added to the Message structure. If the field is not present, it means this message not an external message, or the normalized hash_norm is equal to the regular hash.msg_hash parameter search also by normalized hash.api/v2/sendBocReturnHash returns the normalized hash in addition to the normal hash.external-in) on the TON blockchain was challenging for all of us due to minor metadata differences.?: now correctly works with structs and null valuesget attribute is now correctly showndump() function with an argument of the unsupported StringBuilder type, the error will always be shown even if the debug mode is disabled&&= and ||= augmented assignment operators are now properly short-circuitedStruct.fromSlice(), Message.fromSlice(), and similar functions now work properly if the slice has been parsed entirely and the last field of the struct had the serialization annotation as remaining_ is prohibited for struct and message struct fields, function names, contract, and trait namesreturn statements in the receiver functionscontext().sender, it now calls the sender() function instead to optimize the gas usageinternalExternalReceiversOutsideMethodsMap option and its respective receiver order optimization were reworked to ensure compatibility with explorers and user walletsSendPayGasSeparately constant was deprecated in favor of SendPayFwdFeesSeparately — they're functionally identical, but the latter better expresses the intent and action that this optional flag makes when sending messagesStoppable trait now throws the exit code 133 instead of the exit code generated by the require() function from the "Contract stopped" message
npm install @tonconnect/ui-react@latest or npm install @tonconnect/ui@latest
🥇 1st place: $3000
🥈 2nd place: $2000
🥉 3rd place: $1000int32, uint64, etc.coins and function ton("0.05")bytesN and bitsN (backed by slices at TVM)"..."c postfixes with stringCrc32("...") functions
counterIncrement
counter_id:int32
inc_by:int64
= CounterIncrement;
Maybe int32? Would we write:Both (Maybe int32) int64?as syntax. No ambiguity.int32 and similar:intN (fixed integers), bytesN (definite slices), coins (variadic integers), and some more additions. Read the details in the PR.Either L R and even more complex TL/B structures be expressed? 
