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
franciscoaguirre opened this issue
Mar 26, 2024
· 2 comments
· May be fixed by #4378
Labels
C1-mentorA task where a mentor is available. Please indicate in the issue who the mentor could be.D0-easyCan be fixed primarily by duplicating and adapting code by an intermediate coder.T6-XCMThis PR/Issue is related to XCM.
meanwhile, all other versioned types use the versioned_type macro to get some automatic functionality.
Is there a reason for this? Should we just use the macro for this type as well?
The text was updated successfully, but these errors were encountered:
franciscoaguirre
added
T6-XCM
This PR/Issue is related to XCM.
C1-mentor
A task where a mentor is available. Please indicate in the issue who the mentor could be.
D0-easy
Can be fixed primarily by duplicating and adapting code by an intermediate coder.
labels
Mar 26, 2024
My guess is that it's because of the type parameter RuntimeCall - pub enum VersionedXcm<RuntimeCall>, and it seems like the only difference in the derive stuff is #[scale_info(bounds(), skip_type_params(RuntimeCall))].
C1-mentorA task where a mentor is available. Please indicate in the issue who the mentor could be.D0-easyCan be fixed primarily by duplicating and adapting code by an intermediate coder.T6-XCMThis PR/Issue is related to XCM.
The
VersionedXcm
type is defined like so:meanwhile, all other versioned types use the
versioned_type
macro to get some automatic functionality.Is there a reason for this? Should we just use the macro for this type as well?
The text was updated successfully, but these errors were encountered: