Module error 

Typed parse errors for the OxDock DSL (issue #143).

Beginners must always learn WHAT they did wrong: line and column, what was found, what was expected, and a concrete example. A syntax error must never surface as a bare unknown command: X.

String and file parsers populate line, column span, and source line from pest spans. Token stream parsers (macro_input.rs) set source_line to None and forward the compiler span instead, since proc_macro2::Span carries coordinates but not source text.

Structs

ParseError

Typed parse error with structured diagnostics and a backwards compatible Display rendering.

SpanContext

Location and diagnostic context threaded through lowering.

Enums

ParseErrorKind

Machine readable classification of a parse failure.

Type Aliases

ParseResult

Backwards compatible result alias for parser entrypoints. Public functions return ParseResult directly instead of erasing into anyhow::Error, so downstream crates match statically.