Serialization and deserialization of nested enums would not match. #5
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.
MOTIVATION
There was a small bug where the serialization and deserialization of nested
enums would not match, so a fork created of diem/bcs in the Zefchain org, applied the fix, and
then released v0.1.4 of bcs to crates.io
The fixes done in Zefchain branch, are incorporated in forked repo of Diem bcs and then merged with diem/diem.
-fixes are applied in diem bcs version 0.1.3 regarding the matching of serialization and de-serialization
of Nested enums and updating it to version 0.1.4.
-Then, building diem bcs version 0.1.4.
-referring diem bcs version 0.1.4 to diem code base.
DESCRIPTION
The fixes done in Zefchain branch, are incorporated in forked repo of Diem bcs and then merged with diem/diem.
First step is to apply the fixes in diem bcs version 0.1.3 regarding the matching of serialization and de-serialization
of Nested enums and updating it to version 0.1.4.
Then, building diem bcs version 0.1.4 and performing unit testing for fn test_recursion_limit() :
After successful build and testing, referring diem bcs version 0.1.4 to diem code base.
To refer, first making changes in bcs of cargo.toml file of a single module (Applying path of diem bcs- )
5.After successful build of a single module, further applying the changes in all the modules by giving address of diem bcs in cargo.toml file.