Prep for 0.14 Release #44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lexnv
approved these changes
Feb 27, 2024
niklasad1
approved these changes
Feb 27, 2024
jsdw
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
0.14.0 (2024-02-27)
Changed
The crate now uses
scale-type-resolverto be generic over the provider of type information that is used when encoding and decodingValues.One implication is that
scale_decode::IntoVisitoris now only implemented forValue<()>and no longer forValue<u32>. SoValue::decode_from_type()cannot be used anymore to create aValue<u32>that keeps type id information. Instead you now usescale_value::scale::decode_as_type()which can return the desiredValue<u32>.