devtempmac

> This solved my case: > > `sudo npm install -g bun` yes that could work for some cases... but in my case, with some `require main` checks to differentiate...

not a problem, but I was hoping to extend qubit to output openrpc spec and use it to codegen other language clients (eg. kotlin, python, swift)

@cospectrum yes 100% panic-free is impossible, but these are really low-hanging fruits. And it gives users choice to use 'panicking' function, or somewhat safer 'could be handled right after' function....

https://stackoverflow.com/questions/56107324/why-does-rust-consider-it-safe-to-leak-memory `unsafe` doesn't mean "does not leak memory" in rust and this memory leak not 100% imageproc's fault, but due to some unsafe+FFI implemention problem of some library I don't...

> But if you call imageproc directly, sometimes its your responsibility to ensure invariants before the call. that'll require a lot of extra conditionals just to check "is it safe...

> At this point I think it just comes down to a value judgement where we disagree. I think that even in a least-effort situation we should attempt to handle...

idk throwing errors and crashing at runtime seems to be the worst behavior -- you get to know about it when client gets to run THAT specific part of the...