3 ms·
It would be a tremendous amount of work, and would take years. Meanwhile, the problems are avoidable. It's not exactly the "rust way" to just remember and avoid
by zanderwohl 2y ago
It would be a tremendous amount of work, and would take years. Meanwhile, the problems are avoidable. It's not exactly the "rust way" to just remember and avoid problems, but everything in language design is compromises.
- IshKebab 2y ago"Impossibru!!" https://github.com/sunfishcode/eyra https://github.com/sunfishcode/eyra Oh look: > Why use Eyra? It fixes Rust's set_var unsoundness issue. The environment-variable implementation leaks memory internally (it is optional, but enabled by default), so setenv etc. are thread-safe.
- kbolino 2y agoThat's quite a trade-off
- IshKebab 2y agoWhat is? Leaking memory? It's going to be a few kB at absolute most. Not an issue unless you are doing something very weird.
- mmastrac 2y agoI think glibc made the same trade-off. It makes sense for most types of programs, but there's certainly a lot of classes of programs that wouldn't take it.
- sunshowers 2y agoThat only works on Linux though right?
- zanderwohl 2y ago> Why not use Eyra? Well, that's a lot of caveats. As I said, it would take years to complete. And it looks like it's well on its way but not near complete.
- dvtkrlbs 2y agoIf I understand it correctly this still doesnt help with downstream dependencies.