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
When a value (e.g. Int) is converted into a String via the ToString shard and then passed to the Msg shard, it gives the following error whereby it seems that the type of the result of ToString is incorrect or undefined, or that Msg has an issue with type checking on the results of ToString:
There is no error when Msg is called on a normal String that has not undergone ToString type conversion
To Reproduce
The following code block will result in the above issue
(defmesh main)
(defshards test-shard [test-value]
test-value (ToString) >= .local-test
;; (IsString) (Log) ;; If this line is run, it will output true, so it is might not be a (ToString) bug
(Msg .local-test)
;; (Msg "Normal string") ;; if this line is run, there is no error
)
(defwire example
(test-shard 3))
(schedule main example)
(run main 1 1)
Expected behavior
It should print "3" normally
The text was updated successfully, but these errors were encountered:
This issue has been clarified. Refer to #673 for a follow-up bug regarding the printed error message.
The behavior that the Msg shard cannot print the value of variables is intentional but not fully correct (as it can still print the value of argument variables). Refer to #674 for the follow up to this issue, and here for the respective issue in documentation.
Describe the bug
When a value (e.g.
Int
) is converted into aString
via theToString
shard and then passed to theMsg
shard, it gives the following error whereby it seems that the type of the result ofToString
is incorrect or undefined, or thatMsg
has an issue with type checking on the results ofToString
:There is no error when
Msg
is called on a normalString
that has not undergoneToString
type conversionTo Reproduce
The following code block will result in the above issue
Expected behavior
It should print "3" normally
The text was updated successfully, but these errors were encountered: