You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should consider adding interface abstraction to BaseType.
This would apply to classes like BaseTuple, BaseVec, and BaseEnumExt etc., which handle values with genericity.
Genericity force on manipulate concrete type, offering the benefit of strongly typed classes.
However, this approach comes with a drawback: we're unable to handle a list of events or a tuple of 'IType'.
The advantages of implementing this are as follows:
In applications with multiple layers, there are instances where a particular layer doesn't require knowledge of the concrete type (due to the absence of operations or modifications).
Reduce complexicity
Support for multiple pallet versions.
Let's engage in further discussion about this! 👍
I will link my PR very soon.
The text was updated successfully, but these errors were encountered:
We should consider adding interface abstraction to BaseType.
This would apply to classes like BaseTuple, BaseVec, and BaseEnumExt etc., which handle values with genericity.
Genericity force on manipulate concrete type, offering the benefit of strongly typed classes.
However, this approach comes with a drawback: we're unable to handle a list of events or a tuple of 'IType'.
The advantages of implementing this are as follows:
Let's engage in further discussion about this! 👍
I will link my PR very soon.
The text was updated successfully, but these errors were encountered: