Create a reader for CBOR (Concise Binary Object Representation), as defined in IETF RFC 7049.
- Initial implementation should be done directly into a test project
- Assume a new, netstandard2.0-based package (hedged bet)
- After the reader and writer are stable and feature complete, schedule an API review
- After API review, and associated changes, split things into ref/src/test with the declared package.
Rough project plan (approximately a PR for each stage, and 3-5 days of work)
The reader is needed before the writer, so writing/testing the writer should not hold up a functioning reader.
Create a reader for CBOR (Concise Binary Object Representation), as defined in IETF RFC 7049.
Rough project plan (approximately a PR for each stage, and 3-5 days of work)
Dictionary<object, object>... key types are heterogeneous.The reader is needed before the writer, so writing/testing the writer should not hold up a functioning reader.