I currently use a custom Debug implementation to print types, which–on top of not being very idiomatic Rust–is inadequate for a few reasons. For one thing, there is not enough context inline in the Type enum to print user-friendly names of custom types. QualTypes also get printed with Debug, which looks even dumber because it uses the custom Debug impl for Type and then wraps it in the stock Rust implementation of Debug for structs.
[ ] Implement simple heuristics to associate user-friendly names with types
[ ] Transition from the custom Debug implementation to a Display impl that has access to Driver and maybe TypeProvider.
I currently use a custom Debug implementation to print types, which–on top of not being very idiomatic Rust–is inadequate for a few reasons. For one thing, there is not enough context inline in the
Typeenum to print user-friendly names of custom types.QualTypesalso get printed withDebug, which looks even dumber because it uses the customDebugimpl forTypeand then wraps it in the stock Rust implementation ofDebugfor structs.Displayimpl that has access toDriverand maybeTypeProvider.