Repository navigation
'core2' dependency is now unmaintained and yanked from crates.io #85
Description
core2 is no longer supported and all of its published versions to crates.io have been yanked. It might be worth considering switching the dependency to core, as recommended in the core2 README.
core is still missing a lot of what is provided by core2/std::io, so an alternative no_std crate that provides an API similar to io will probably be required.
Reacted by Adrian Braemer, Maxim Stykow, WarrenS and Tate, Hongliang Tian
Activity
LockedThread commentedon Apr 14, 2026
Temporarily you can patch it to the previous commit before the yank:
Validate the revision yourself at https://github.com/bbqsrc/core2/tree/545e84bcb0f235b12e21351e0c69767958efe2a7
xanarin commentedon Apr 14, 2026
It seems like
no_std_iomight be an (almost) drop-in replacement, given that it's originally forked fromcore2, but still "officially" maintained.abraemer commentedon Apr 14, 2026
In my PR #86 I replaced core2 with
no_std_io2which is a fork ofno_std_ioxanarin commentedon Apr 14, 2026
Looks like
no_std_io2is more maintained thanno_std_io; good choiceLockedThread commentedon Apr 14, 2026
Related hackyderm thread.
https://hachyderm.io/@piecritic/116404790999620656
sile commentedon Apr 14, 2026
Thank you for creating this issue.
I will review the PR within a week.
workaround core2 being yanked
sile commentedon Apr 15, 2026
I will start reviewing the PR soon.
BTW, I recently prefer to develop library crates with as few dependencies as possible (e.g., nojson, noargs).
So, I started developing noflate (a no-deps DEFLATE library) in the same spirit.
That said, using
no_std_io2seems a reasonable choice for this issue. As a long-term solution, switching tonoflatemight be one option worth considering, though it is not API-compatible withlibflate.sile commentedon Apr 15, 2026
Merged the PR and published libflate v2.3.0.
This was an unfortunate situation, so thank you very much for reporting it and helping address it.