in a sane ecosystem, this would involve distros updating the packages for those few crates
but in the world we live in this not only makes packages that depend on those crates fail to build, but also we have to patch dependencies for every package that breaks, one-by-one.
@navi the rust ecosystem is so ugh: making it interoperate with anything is icky, crates.io is horrible (centralized, does not allow deletion of crates, etc), proc macros are not sandboxed, build.rs has unrestricted side effects, etc...
at least there is a proposal to allow deleting crates, with some restrictions...
still doesn't address the issue of malicious crates being uploaded, though, which is much worse than just a crate getting deleted. i feel they're really focusing on the wrong issues
also, why the heck are they using discord. they're a free software project, using discord is just embarrassing. fuck discord
@navi been saying this for years but the response always ranges from oblivious indifference to "why do you hate memory safety"
the issue kinda becomes way more obvious as soon as you deal with any kind of "weird" scenario (e.g. niche archs, cross-compiling, etc.) because it makes all the issues most people (i.e. x86_64 linux/mac) don't usually see bubble up
@navi@lumi the language has its issues too (every time i have to dig up where something comes from in a hellish spaghetti of trait hierarchies i wish i didn't, and it's overall a bit too symbol-soupy for my taste; all this results in reliance on various tooling where i normally wouldn't have to) but the ecosystem is the main problem yea