Update libc dependency#102
Merged
stouset merged 1 commit intostouset:masterfrom Aug 14, 2025
Merged
Conversation
stouset
approved these changes
Aug 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You don't support libc@0.1. So don't say you do.
Yes, cargo by default will give you libc@0.2, and everything will work. But also, libc could release a version 0.3 with API changes (however unlikely that may be), and you would break because of that. And you don't even have the benefit of allowing a 1.0 libc, either.
You don't necessarily need to be fully minimal-versions correct (though it would be better if you were), but saying you work with libc@0.1 and libc@0.3 is just completely incorrect.