This shows how it could be used with a no-std allocator. Given an allocator, actually nothing is different from std usage.
A presentation of how to force yourself to add .context to your results/errors before returning, so that there will be enough information in error messages.
This demonstrates how libraries could use the error type, while still providing discoverable recovery information and good error messages and interfacing.
This presents how messages for non-developer users could be constructed without losing information for developers debugging the thing.
Demonstration of interactions with ExitCode and general bubbling up.
An example of stacking multiple validation errors together ergonomically.
Recovering from retryable errors in a web client application.
Integration into common webserver backends to provide adequate automatic error responses.