The sdk macro generates code, for the json case, in such a way that the user, when building a request message, must (read as: can) actually name the arguments. As we know, in normal and direct method invocation in rust, we cannot name them, so named arguments are quite a profound of a feature.
This project tries to follow that decision, and will also should try to offer ways to opt-out from the naming of arguments, as there are genuine (possibly cost-saving) cases where this could be desired.
Related: #10
Related feature: serde attributes also allows for having arbitrary argument positioning, having (and ignoring) extra arguments, which are also interesting (but possibly dangerous) features for composability.
The sdk macro generates code, for the json case, in such a way that the user, when building a request message, must (read as: can) actually name the arguments. As we know, in normal and direct method invocation in rust, we cannot name them, so named arguments are quite a profound of a feature.
This project tries to follow that decision, and will also should try to offer ways to opt-out from the naming of arguments, as there are genuine (possibly cost-saving) cases where this could be desired.
Related: #10
Related feature: serde attributes also allows for having arbitrary argument positioning, having (and ignoring) extra arguments, which are also interesting (but possibly dangerous) features for composability.