Fair enough. > the framework should not assume there is one best/default way Best, probably not. Default, I'd argue that Rust's approach of defining Display

Fair enough. > the framework should not assume there is one best/default way Best, probably not. Default, I'd argue that Rust's approach of defining Display and Debug traits (interfaces) in the stdlib is reasonable. It is explicit, specific, and unambiguous. While having a trait system helps a lot, it's not hard to imagine instead of a single `ToString()` defined by Object, it has `ToDebugString()`, `ToDisplayString()`, etc..