Overly verbose output error message on .unwrap()

[Satellile]

The issue is well described here: https://users.rust-lang.org/t/serde-toml-error-reporting/127521

When using

let val = toml::from_slice(&bytes).unwrap();

the terminal output is very verbose and hard to read.

Doing it as:

let val: EventFile = match toml::from_slice(&bytes) {
    Ok(s) => s,
    Err(e) => panic!("{e}"),
};

yields the expected beautiful and readable output, which makes it easy to find where the parse issue occurred in the toml file. But this makes the code a bit needlessly verbose.

I think it would be ideal if, like with serde_json, unwrap produced the terse output.

[epage]

Looking at serde_json (https://docs.rs/crate/serde_json/1.0.149/source/src/error.rs#425), they aren't showing the Display impl but remove layers from wrapper types.

We don't track line numbers but byte offsets so that shows up.

Maybe worth dropping the original input that we use for rendering errors.

Overall though, panicking / unwrapping is generally treated as an assert / development time bug (which shows in the fact that Debug is used) so having user facing debug output / development errors is not something I'm open to.