1. Get started
Build the crate, construct every profile field, and run the maintained parser and writer examples.
Choose a parsing or writing task.
Start with the parser or writer boundary that your application controls. Each guide keeps storage, profiles, publication, and failure behavior explicit.
Task guides
2. Parse chunks
Use Flyology_CBOR.Parsing with arbitrary input bounds, provisional events, and exact byte offsets.
3. Write a document
Use Bounded_Writing, allocating storage, or a caller-supplied destination transaction.
4. Preserve raw values
Keep Values representation separate from checked integer and binary64 conversion.
5. Select behavior explicitly
Construct Parser_Profile and Writer_Profile without a public default.
6. Check the boundary
Review implemented support, maintained evidence, known omissions, public source availability, and Alire index status.
Reading path
Choose how much data to retain.
The parser has no DOM or collector. A consumer can handle each event immediately, copy selected payloads into its own storage, or build a provisional candidate until the parser reports complete-document acceptance.
Read and discard
Use Drain to inspect a large stream with a bounded parser and caller-owned event array.
Retain a few values
Copy only the text, bytes, numbers, or tags that the application needs.
Commit after acceptance
Keep a private candidate provisional until the parser reports complete-document acceptance.