Input bounds

Every parser treats its input as hostile. Counts, sizes, recursion depth, work and output are capped by named constants. cargo xtask regen generates this page from every module-level constant in crates/*/src whose name starts with MAX_ or ends with _LIMIT, _BUDGET or _CAP, and cargo xtask regen --check fails when it is stale. The kind column is derived from the constant name.

The exceeded column states what happens when input goes past the bound. It comes from a syntax-tree scan of the defining crate's non-test sources: each read of the constant is traced through comparisons, local bindings, struct fields, same-crate function parameters, function results and derived constants to the branch taken when the bound is exceeded. The column reports the strongest outcome over all reads, in this order:

• error: a typed error is returned. The column names the error variant and its DR- diagnostic code when the variant carries one; untyped marks a string error.
• recorded: the input is truncated or refused and a flag or refusal record says so.
• panic: an assertion or panic fires.
• delegated: the bound is passed to a function the scan could not follow.
• silent: a loop stops, a value is clamped or work is skipped with no error and no record.
• unclassified: the scan found a read but could not attribute an outcome to it.
• allocation: the bound only sizes a buffer or a capacity reservation.
• unused: the defining crate never reads the constant.

The scan does not resolve types or trait dispatch, so an outcome names the construct it found rather than proving the behaviour.

2225 bounds (count 217, other 1039, output 67, recursion 228, size 488, work 186).

Exceeded: error 900, recorded 191, panic 0, delegated 49, silent 1026, unclassified 18, allocation 33, unused 8.