miette
miette copied to clipboard
zkat
Fancy extension for std::error::Error with pretty, detailed diagnostic printing.
... or, please, add any other way to pass multiple diagnostics at once to create a single report
If an error or variant has an error code, we should add a ``#[doc = "_Error code_: `{code}`]`` to them automatically so they show up in the documentation.
It looks like `Report` can be casted to diagnostic reference, since it implements `AsRef`. But I can't find an implementation of `Diagnostic` for `Report` itself for some reason. It could...
The description for `MietteHandler` says: `See set_hook for more details on customizing your global printer.` But all docs for `set_hook` say is: `Set the error hook.`
It would be grate to have at least basic (without caching and etc.) struct that implements `SourceCode` E.g: ```rs struct SourceFile { path: PathBuf } impl SourceCode
Sometimes, I want to construct a bigger error from several related ones. It happens either from convenience reasons, or from technical ones (part of the error may be located in...
`SpanContents` may be itself a valid source for diagnostics. Contrary to `String` source, which provides source code from line `0` and column `0`, `SpanContents` can provide sources starting from any...
If the error message contains some ANSI escape sequences, for example to make part of the message stand out. Then they get broken when the error message gets big and...
I observed that diagnostic information is not rendered when an error is wrapped using `wrap_err()` even though it should be (if I understand #170 and #172 correctly). Example: ```rust fn...
This could be useful for creating and modifying a dynamic diagnostic using an already existing diagnostic.
