Deriving structural interfaces for contracts

[hashedone]

This is a tracking issue for #391.

• Reimplement cw1-whitelist contract in terms of semantic structures #494
• Implement attribute macro for trait interface generating boilerplate specific for cw1-whitelist #495
• Update reimplemented cw1-whitelist contract, so it uses the custom attribute #496
• ...

[ethanfrey]

Thanks for preparing this list of concrete steps.

I would add

Reimplement cw1-subkeys as an extension of reimplemented cw1-whitelist

Maybe as step 2. This is essential functionality and working this out will give a lot more clarity on limitations to all the traits and other restrictions, or what other macros would be useful.

[hashedone]

There are basically for that - I picked the cw1-whitelist as an initial one, as it uses minimal subset of features to generate. cw1-subkeys introduces additional think, which is generic messages. It is important to support those, but as next step. Also important step would be add a contract which implements more than one interface (eg. any contract fulfilling interface of cw20 Receive). It is on the way, but wanted to postpone decision which one is actually the best as next one to the moment when there is some implementation of generation (to decide which extension is the easiest to come with).

[uint]

This is already being worked on in Sylvia. Closing!