One serialization / encoding scheme
@rafal-ch is already working on this.
Since Apr 1, 2022.
Assessment
This issue has not been assessed yet.
Description
Enhance existing bytesrepr to optimize using write_bytes and also identify and correct places in the code where we deserialize unnecessarily. The codebase has grown organically over time, and due to tight timelines, there was no standard serialization/deserialization scheme put in place. This has led to 2 issues:
- Multiple serialization/deserialization solutions in use and
- the need to serialize/deserialize data unnecessarily because they don't use the same mechanism
This feature will contain at least the following tasks:
- Research and identify all the different mechanisms in use in the code
- Align on a standard for serialization
- migrate all non-standard mechanisms to the standard
- remove all unnecessary serialization/deserialization
- Dominant language
- No language data
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from casper-network/roadmap
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
casper-network/roadmap#228 ·
-
Epic
Difficulty 5/5 Over a week Newbie friendliness 15/100
casper-network/roadmap#214 ·
-
DiscoveryOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
casper-network/roadmap#210 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
casper-network/roadmap#208 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
casper-network/roadmap#207 ·