receive(msg: Slice) is not available for users to call

[anton-trunov]

This contract

import "@stdlib/deploy";

contract MyContract with Deployable {
    receive("foo") { dump("1") }
    receive(msg: String) { dump("2") }
    receive(msg: Slice) { dump("3") }
}

results in the following receivers:

Related Tact docs page: https://docs.tact-lang.org/book/receive/#receive-internal-messages

[rahulyadav-57]

For the Slice type, I am currently receiving message.kind: any. Should I prompt the user to select a cell file as input in this scenario?

Regarding the String type, it currently appears blank, as shown in the attached screenshot. Instead of leaving it empty, we can display "string" or "text" when message.kind = "text" and the text property is not provided.

"message": {
    "kind": "text"
}

[anton-trunov]

Should I prompt the user to select a cell file as input in this scenario?

Or we could ask them to provide a constant slice expression, like emptySlice(), rawSlice("4a_") or slice("te6cckEBAQEADgAAGEhlbGxvIHdvcmxkIXgtxbw="), see https://docs.tact-lang.org/ref/core-comptime.

Tagging @novusnota for more ideas

[novusnota]

Agree with @rahulyadav-57 and @anton-trunov. Adding anything extra would not be beneficial to the end-user, who is probably someone advanced and have their own workflow of composing cells/slices/etc., so we just need a simple way to accept those.

Thus, to re-iterate:

1. In case of String, instead of the current "": the user should probably see String: and then be allowed to type the String with or without the surrounding double-quotes "".

2. In case of Slice, the user will see Comptime Slice expression: and the hint saying For example, rawSlice("4a_").

To implement the latter, import the parseAndEvalExpression() function from src/interpreter.ts, and only provide the string as the first argument.

[rahulyadav-57]

Thanks for the inputs. We can go with the approach.