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 dfx call takes an opt type, the opt subtyping rule essentially turns off the type checking. We need to disable or at least warn about the use of opt subtyping rules in the parser.
The text was updated successfully, but these errors were encountered:
I wonder how useful it is in general to apply subtyping here. Subtyping is meant to be used when A sends a message to B according to an old B.did, so really only should play a role during decoding a message from another party.
When A is a CLI interface that parses a textual argument according to A’s believe of B’s interface, we don’t need to apply full subtyping, we merely need to use B.did to help resolve overloading, and maybe for convenience stuff (e.g. omitting optional arguments).
I don’t see a point in ignoring additional record fields, doing the full opt-field handling etc.
when
dfx call
takes anopt
type, the opt subtyping rule essentially turns off the type checking. We need to disable or at least warn about the use of opt subtyping rules in the parser.The text was updated successfully, but these errors were encountered: