The current maintainer of bincode has explicitly stated that the project is not maintained anymore, and nobody should be filing issues on it:
If you're so bothered by this just use the 1.x bincodes. Seriously. It's done. For years any issues always turned out to be user error. There's never once been a CVE and if there is we trust that the person finding it will be smart enough to find us. (And also less of a tax on our mental health).
Filing issues for 2.x? Don't. I don't care. It's bincode. It's dead simple. I'll get around to finding the issues myself. Maybe. When I get back into programming. Eventually.
As such, I think that bincode support should not be forward-ported to smallvec 2, as we should be encouraging the ecosystem to migrate away from it and use other serialization frameworks.
The current maintainer of bincode has explicitly stated that the project is not maintained anymore, and nobody should be filing issues on it:
As such, I think that bincode support should not be forward-ported to smallvec 2, as we should be encouraging the ecosystem to migrate away from it and use other serialization frameworks.