parse-net 0.9.3

Grammar for Internet message fields: RFC 9110 field syntax, media types, RFC 9651 Structured Fields, HTTP and RFC 5322 dates, negotiation, entity tags, ranges, Content-Disposition, Cache-Control, Forwarded, auth challenges, and the email lexical layer. no_std, no allocation, sans-IO, zero dependencies.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

# parse-net v0.8.0 - Alpha

**Date:** 2026-10-29
**Compare:** [`v0.7.0...v0.8.0`](https://github.com/jamesgober/parse-net/compare/v0.7.0...v0.8.0)

**In use.** Three published crates now take their HTTP and mail grammar from parse-net, with green CI and no API change requested. v0.8.0 records that, fixes the weekly differential fuzz workflow, makes the complexity tests stable on every CI runner, and adds the pre-1.0 polish pass to the roadmap. The library code and the API are those of 0.7.0.

## Consumers

| Crate | Versions on parse-net | Requirement |
|---|---|---|
| http-net | 0.8.0, 0.9.0 (its only runtime dependency) | `^0.7` |
| cookie-net | 0.3.0 to 0.7.0 | `^0.6.1` |
| form-net | 0.3.0 to 0.5.0 | `^0.6.1` |

serve-net and LexerSketch Studio run against http-net on parse-net with no change. ws-net, the other planned 0.8 consumer, still carries its own grammar; it moves to 0.9 with smtp-net and web-net.

## Changed

- The weekly differential fuzz workflow builds for `x86_64-unknown-linux-gnu`. The cargo-fuzz installed by `install-action` is a musl build and defaulted to its own target, where the address sanitizer cannot link, so the first run built nothing. A run from the fix fuzzed `diff_http_date` (467 million runs), `diff_media_type` (174 million), and `diff_sfv` (14 million) for 30 minutes each, clean.
- The complexity tests check timing on an optimised build only, in the `Complexity (release)` CI job at the 1.2 bound. A debug build on a macOS runner measured 2.23 from 64 KiB to 1 MiB on `parse_quoted`, a single loop, so an unoptimised build now checks the limit errors and prints the times (D-073).

## Roadmap

- A pre-1.0 polish pass in 0.9.x, before the first release candidate: every accepted gap, deferred item, known issue, and missed target revisited (the `encode-lib` helpers, `client_address` against its estimate, the narrowest benchmark margins, form-net's `FormKind::detect` at 114 ns against 100 ns, the fixed 64-parameter table, the ambiguous differential verdicts); a fresh performance pass; the security and edge-case review again. Whatever is still open goes in the 1.0 readiness note for James.

## Compatibility

- No API change. MSRV 1.85, edition 2024, `no_std` without `alloc`, zero runtime dependencies. Consumers on `^0.7` keep 0.7.0 until they raise their requirement; nothing in 0.8.0 changes what they get.

## Verification

- Local gate on Windows and WSL Ubuntu, Rust 1.99 and 1.85: format, clippy with default, all, and no default features under `-D warnings`, tests in the same three modes, documentation under `-D warnings`, the bare-metal build, and `cargo package`.
- Banned-content and link checks over every shipped file.

## What's next

`0.9.0`: beta. ws-net, smtp-net, and web-net on parse-net, the pre-1.0 polish pass, and the `0.9.x` release candidates.

**Full Changelog:** https://github.com/jamesgober/parse-net/compare/v0.7.0...v0.8.0