Andreas Rossberg
Andreas Rossberg
As mentioned elsewhere, I think I'm fine if this works just for a fixed arity for now. The wallet example could add methods for different return arities if that's needed....
@matthewhammer: > To me, it seems reasonable to treat these dyn values as something that require explicit language primitives, or even a library, to intro and elim in Motoko (or...
> My thinking was that the MVP would merely introduce dynamic as a special kind of Blob that is always encoding an argument sequence in Candid Hm, an argument sequence...
> Well, no, only the methods that are to be used in a higher-order _and_ generic way need to use this type. Hm, I believe it's a crucial point for...
Okay, I extended the proposal with proper support for gradual typing.
I just noticed that the sketched http_request interface also works around the lack of a generic type, as it has this: ``` // There is no generics in Candid, so...
@hansl, I think what you have in mind would essentially turn Candid into an untyped language, with all sorts of implicit conversions being made on the receiving end. That would...
Oops. The dreaded subtype check again. :(
Hm, yes, this sounds plausible and attractive to me. Just one question for clarification, You said: > We go back to backtracking decoding with `opt`, but we decode _typed_ values,...
For the time being I think it's fine if this pattern only worked for functions of fixed arity. If we wanted variadic abstraction, maybe we could make a tuple record...