I kinda like the `.or_panic()` name. In an ideal world where Rust has optional parameters and anonymous unions (still tagged), I'd even see a single `.or_panic(msg: &str | None = None)` method to reduce verbosity (but this is obviously fictional and subjective).

oh i just realized i was only thinking about the variance of type parameters, if we are talking about the variance of function parameters then i agree it is very much unsound and evil

by "by default", do you mean whenever a type parameter is unused? if so, does this often happen? i fail to see the problem tbh

Yay!

Yah I used to check that sub somewhat regularly and I agree, I hope some non-Discord alternative will emerge in the future

All of that to say: do not abbreviate your "term" variable to "trm", it is not worth it.

Still, I am convinced there is objective truth in what is or is not good code. I swear one day I will make blog posts on how I personally write "good code".

Broke: frontend vs backend
Woke: revenue generator vs cost center

Also use PascalCase even for primitives types, use `Never` for the never type (why use a symbol for something so rare !), and a pronounceable keyword for functions (`fun`, `func`, `def`...).

On more controversial topics, I would use kebab-case for identifiers (IMO the most readable naming convention, although quite rare unfortunately), use `.` everywhere instead of `::` (so ugly !), and use indentation-sensitive grammar instead of braces.

Hhhhm, on the hot topic of language syntax, I would have a single expression for pattern matching (`is` or `let` expression, like the contentious RFC of last year) and use `[]` instead of `<>` for generics (byebye turbofish).

Damn I thought the logo was pretty uninspired but now I really like it, nice.