You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tact compiler allows specifying remaining as a serialization format for map values, despite that it doesn't actually do anything and default still applies. Consider the following example:
contract Example {
m: map<Int, Cell as remaining>; // ← compiles fine,
// albeit as `dict<uint8, ^cell>`, and not
// `dict<uint8, remainder<cell>>` as one might expect
}
However, tact-vscode considers it an error, showing Unsupported format remaining for map value, while the code compiles just fine under Tact v1.4.0 and newest dev versions, see: tact-lang/tact#569 (comment)
The text was updated successfully, but these errors were encountered:
Tact compiler allows specifying
remaining
as a serialization format for map values, despite that it doesn't actually do anything and default still applies. Consider the following example:However, tact-vscode considers it an error, showing
Unsupported format remaining for map value
, while the code compiles just fine under Tact v1.4.0 and newest dev versions, see: tact-lang/tact#569 (comment)The text was updated successfully, but these errors were encountered: