I agree with you that the documentation for many modules in general, and overload in particular leaves much to be desired. I've had several attempts at using overload in earnest for things that go beyond the simplistic--and asked here for further information--without much success with the more esoteric uses.

That's one of the reasons I'd like to see the current practice of writing a zillion small, useless tests (the code being tested, not the test itself!), replaced by a single, simple but complete application of the module, with the current individual tests achieved by assertions.

If all the tests complete successfully, the test application finished with a simple "All passed" message. It's all the user needs to know.

If an individual assertion fails, the test application terminates with the line number at which it failed plus full trace back. This tells the developer what failed and where.

And the test application acts as documentation for the user programmer.