Path Normalization

Path normalization follows Name & Reference Resolution and precedes Coherence. It rewrites resolved multi-segment paths into identity-bearing forms consumed by later stages, producing the boundary type that proves the rewrite has run. Owning crate: metel-frontend; implementation: path_normalizer.rs.

Verifiable architecture claims

Owner metel-frontend unless a requirement names another.

Requirement №1

Multi-segment qualified paths (Expr::Path, e.g. math::sin) rewrite to Expr::ResolvedPath carrying the resolved SymbolId, producing a NormalizedModuleGraph whose fields are pub(crate), so only path_normalizer::normalize can construct one.

Related: ADR-0021, ADR-0031

Implemented by (1)

• normalize metel-frontend/src/pipeline/path_normalization/mod.rs

Tested by (4)

• normalized_graph_can_only_be_built_inside_this_crate metel-frontend/src/pipeline/path_normalization/mod.rs
• explicitly_imported_qualified_call_carries_the_same_symbol_id metel-frontend/src/pipeline/path_normalization/tests.rs
• glob_imported_qualified_call_carries_a_symbol_id metel-frontend/src/pipeline/path_normalization/tests.rs
• self_qualified_call_carries_a_symbol_id metel-frontend/src/pipeline/path_normalization/tests.rs

Known limitations

knownLIMIT-PATH-NORMALIZATION-001 — root::/super:: are rejected in expression position when the target is declared directly in that module. root::name and super::name work through a submodule path but are rejected in expression position when name is declared directly in the root or parent module. Open record ↗