Open novusnota opened 4 days ago
What do you mean by "fails silently"? I've just ran that code and it resulted exit code 9 - just as expected.
@Gusarich Let's add a failing test to the test suite to resolve the issue
@novusnota So it looks like indeed the dump
s do not work because execution fails with the Cell Underflow error message
What do you mean by "fails silently"?
Testing in Blueprint via Sandbox and Jest don't show anything if one is looking at dump()
output. I see that tact-emulator
shows the error, but most of the Tact users are working in Blueprint
P.S.: It would be nice to synchronize those two (tact-emulator and sandbox) in the future somehow
@novusnota Please open an issue in Blueprint's repo (if it's somehow a sandbox issue we'll just move it there)
P.S.: It would be nice to syncronize those two (tact-emulator and sandbox) in the future somehow
It should be Sandbox
@novusnota Please open an issue in Blueprint's repo (if it's somehow a sandbox issue we'll just move it there)
@novusnota Thanks!
Btw, here is a new related issue: #510
Consider the following snippet:
Although it's up to user to correctly specify serialization modifiers, such as
uint32
and then use.storeUint(NUM_TO_STORE, 32)
and similar, it would be nice to display an error when mistakes occur.This may be an edge case of some bigger issue.
Also it's unknown what value
coin
has in the showcased example, because an attempt todump(coin)
will be prohibited asdump()
doesn't support Structs and Messages directly and type ofcoin
is still considered to beCoin
.P.S.: Kinda offtopic, but this reminded me that we may consider adding
.storeUint32()
,.storeUint64()
and similar functions for convenience. Or, to make a special function for Ints, which would accept serialization modifiers, like so: