API and support map¶
Use the references below for API contracts, implementation gaps, and backend support. Rustdoc documents unimplemented public methods on the methods themselves; an API appearing in Rustdoc does not by itself mean it is implemented. Converter coverage describes available lowerings, while WPT results describe tested numerical behavior.
This navigation table replaces the former Implementation Status, API Overview, Backends, Advanced Topics, and WebNN Specification guides. Graph-file guidance is consolidated below.
| Topic | Authoritative reference |
|---|---|
| API entry point and first graph | Crate Rustdoc |
| Context operations and unimplemented methods | MLContext, including op_support_limits |
| Builder operations, naming conventions, and constant-construction gaps | Builder module, MLGraphBuilder |
| Tensor access, lifetime, and unimplemented methods | MLTensor |
| WebNN dictionaries, defaults, and enums | Options, enums |
| Backend selection and feature flags | Selection rules, crate features |
| Backend setup, caching, precision, and limitations | TensorRT-RTX, CoreML, LiteRT, CANN, browser WebNN; ONNX Runtime setup |
| Operations lowered by each backend | Generated operator support report |
| Tested numerical conformance and remaining failures | WPT dashboard, test and baseline workflow |
| Dynamic shapes and tensor capacity | Dynamic-shape workflow, runtime validation |
| Graph files, external weights, loading, and saving | Shared graph-file guide |
| Backend conversion and graph architecture | Converter guide, architecture |
| Logging, tracing, and model dumps | Diagnostics, environment variables |
| Errors and troubleshooting | Error types, troubleshooting |
API comments link to the relevant WebNN specification sections. Consult those comments for Rust-specific differences rather than maintaining a separate specification-to-API inventory.