1. Get started
Build the crate, construct every profile field, and parse a complete value through the public surface.
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.
2. Parse chunks
Use Flyology_JSON.Parsing with arbitrary input boundaries, provisional events, and exact source ranges.
3. Write a document
Instantiate Flyology_JSON.Writing over a destination that stages a complete transaction.
4. Retain selected tokens
Copy selected fragments with Flyology_JSON.Tokens, then convert complete integer lexemes.
5. Select policy explicitly
Build Parser_Profile and writer profiles without a public default.
6. Check the boundary
Review implemented support, tested toolchains, known omissions, and the pre-release dependency gate.
Reading path
Choose by the value you need.
The core has no DOM. A consumer can handle each event immediately, copy selected strings into bounded storage, or build its own unpublished candidate until the document completes.
Read and discard
Use Drain to inspect a large stream with bounded parser and event storage.
Retain a few values
Collect only the names, strings, or numbers that the application needs.
Commit after acceptance
Keep a private candidate provisional until the parser returns complete-document acceptance.