Vision: Pallet syntax improvement

[ggwpez]

Some ideas that came up in recent meetings and discussions on how to improve the pallet syntax:

• Removing the explicit generate_deposit and rather having a deposit function on the event type itself (eg via #[derive(Deposit)]).
• Making the <T> on the pallet Event and Error optional Pallet Syntax: Analysis of T consistency #176.
• Getting rid of trivial #[pallet::weight(T::WeightInfo::call())] by having a pallet weight_info pallet attribute that provides the WeightInfo and then tries to pull it from there FRAME: inherited call weight syntax substrate#13932.
• Breaking pallets into smaller parts: [FRAME Core] Adds ability to split a pallet across multiple files substrate#13950
• Default hashers in dev-mode Optional storage hashers in pallet dev mode substrate#13263
• (unconfirmed) Removing fn getters: remove storage getters in FRAME substrate#13365 / [Deprecation] remove storage getters in FRAME #223
• Check if we need generate_storage_info

Please edit to extend.

[bkchr]

• and Error optional.

That doesn't work. We need T for Error to get the pallet index.

[lsroudi]

really it take time to learn the syntax, this changes regarding the syntax for me should be scheduled but it is not the important one

[kianenigma]

Making the on the pallet Event and Error optional

I am not sure if this is the way forward tbh. I wish I could come up with a single rule that would rule all of the #[pallet] enhanced types, but especially because of Event and GenesisConfig, I cannot. These two can correctly have no generic, and this makes it tricky.