3 ms·
The "caveats" section in its docs hints at it, but to be explicit: no_panic is a band-aid that can break when changing optimizer options or compiler/llvm versio
by krautsauer 7mo ago
The "caveats" section in its docs hints at it, but to be explicit: no_panic is a band-aid that can break when changing optimizer options or compiler/llvm version. It's not a good option for library crates, e.g.
That being said, I'm not at all happy with all the complexity and ecosystem fragmentation that async brought. I understand what you're saying. But surprise panics is a bit of a pain point for me.
- dtolnay 7mo ago> It's not a good option for library crates, e.g. Author here. Yes, it is. It was literally made for libraries. Notably https://github.com/dtolnay/zmij https://github.com/dtolnay/zmij and https://github.com/dtolnay/itoa https://github.com/dtolnay/itoa use it to enforce that the libraries' public API is absent of panicking.