The call_builder
macro to provide a more developer-friendly way to work with CallBuilder
#1742
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Implemented the
call_builder!
macro from the proposal.The macro return the
CallBuilder
type that supports hinting and highlighting in the IDE.The usage is the same as for standard cross-contract calls, where the call is wrapped into the
call_builder
macro:How it looks in the IDE:
Follow-up
create_builder!
macro for constructors in the follow-up PR. It would simplify instantiation because all functions will be highlighted. The macro would be much simpler because it always requires an explicit type name.mesage_descriptor!
macro that returns theMessageDescription
. Everyone would be able to get the method's selector(and other properties of the message) like in the soliditymessage_descriptor!(self.balanec_of).selector()
.TraitCallBuilder
and replace its functionality with a new macro. Remove the{method_ident}Output
associated type from the trait definition.