feat: Remove Clone trait from ExtnMessage #484
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.
What
Removes the Clone trait from Extn Messages
Why
Based on a cargo bloat Run ExtnMessage and its enums have the most size in the executable. Major contributor for this is the Clone Trait
How
Given Serialization and Deserialization is already inherent in the ExtnMessage clone trait is redundant.
Test
Run Cargo bloat again and validate the results with and without these changes
Checklist