Ok, I then have some business proposals....

Are you saying that it is common that people use utf8 characters that you cannot easily type on a standard keyboard? I'm very skeptical of this claim.

Splits, ligatures tabs and more

Of course cars would loose if you tried to use it to travel across the Atlantic...

Well, what I want to know is "Am I going to die today?". The distance traveled is irrelevant to answer that question. The only reason to add that to the equation is to make air travel look safer.

Weird, a blog post by Collabora about a crate by Collabora, that no longer is availabe? Well, the crate seems to be, but not the code. So, what is going on here?

Didn't know about this, looking forward for this to be stabilized. But a comment on your command, it is easier to use --all-features instead of listing them all.

I'm not the author, but thanks for the link.

You are right, it does. But as you say, it seems more limited in that aspect than error-stack from a first glance.

It should be, in the ideal world, just be thrown as a last resort... but in reality it isn't. I assume it is because when you find a nice IllegalStateException, you might feel that it really describes your condition quite well, so you use that without realizing that it is a surprise exception since that is not very clear. When you are using your IDE and need to throw an exception in an error case, it is not clear what is a runtime exception and not, and then you are not forced to use throws and here we are...

The equivalent in Rust would be to have a std::error::GenericError(String) in rust, that looks like a normal error but secretly panics under the hood.