3 ms·
Yep, exactly something like this! Implementation is the challenging part: the standard library and community ecosystem is full of legitimate uses of panic, and
by woodruffw 5y ago
Yep, exactly something like this!
Implementation is the challenging part: the standard library and community ecosystem is full of legitimate uses of panic, and there are instances where panics might appear in the source code of dependencies but not in (optimized) builds.
- nicoburns 5y ago> full of legitimate uses of panic Yes, but the whole point of `no_panic` is that in this context there are no legitimate uses of panic. If that means making a bunch of parallel APIs that return results for this super-correct code then so be it.
- woodruffw 5y agoYou're absolutely right. I meant primarily in terms of the challenge of writing panic-free code while still being a consumer of the crate ecosystem.