0kenx
0kenx
The current semantics of options is Tact is quite lengthy. It would be nice if it could be improved. Reference: https://doc.rust-lang.org/std/option/enum.Option.html To begin with, having `unwrap_or` would be very nice....
Currently it's not possible to use `break` from within a loop.
## Example File A.tact: ```kotlin import "./B.tact"; import "./C.tact"; contract A with B {} ``` File B.tact ```kotlin message(0x5555AAAA) M {} trait B {} ``` File C.tact ```kotlin message(0x5555AAAA) M...
ICRC-19 - Rebase Token Standard Data Details icrc: 19 title: ICRC-19 Rebase Token Standard author: @0kenx status: Deliberating category: ICRC requires: ICRC-1 created: 2023-03-23 updated: 2023-03-23 # Context The ICRC-1...
Mathlib `ton/crypto/smartcont/mathlib.fc` crashes when trying to use `fixed248_log2`. ## What behavior did you expect? Should compile. ## What was the actual behavior? ``` Fift decompiler crashed Error: Unknown opcode: b1111011...
Why does Tact generate the following FunC code: ``` slice __tact_verify_address(slice address) inline { throw_unless(136, address.slice_bits() == 267); var h = address.preload_uint(11); throw_if(137, h == 1279); throw_unless(136, h == 1024);...
It's quite easy for Tact to support arbitrary precision numbers such as `int4` `uint22` `uint160` etc. This would save gas in many circumstances.
Tact should add support for `Either` TL-B type. I propose we use the `?` operator: TL-B `Either X Y` -> Tact `X ? Y`. If it's too confusing we could...
## Background Currently `npx blueprint build` allows for specifying a build target. However for `npx blueprint test`, it's not possible to specify only 1 file to test, so every time...
When compiling a large project using `npx blueprint build --all`, the following error occurs: ```text (node:3805163) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners()...