-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Comments
[0.2] Increase the MSRV from 1.63 to 1.65#4972
Open
tgross35 wants to merge 1 commit intorust-lang:libc-0.2 from
Open
[0.2] Increase the MSRV from 1.63 to 1.65 #4972tgross35 wants to merge 1 commit intorust-lang:libc-0.2 from
tgross35 wants to merge 1 commit intorust-lang:libc-0.2 from
Conversation
Collaborator
rustbot
commented
Feb 13, 2026
- Pull requests are usually filed against the main branch for this repo, but this one is against libc-0.2. Please double check that you specified the right target!
@tgross35
tgross35
requested review from
Amanieu,
JohnTitor and
joshtriplett
February 13, 2026 06:56
Contributor
Author
tgross35
commented
Feb 13, 2026
I'm not planning to merge this before the next release, just wanted to start collecting reviews.
Open
Perform a small MSRV bump by two versions. The main thing this gets is access to the C types in `core::ffi`, which means the ecosystem can start harmonizing around those aliases instead of using e.g. `core::ffi::c_int` in some cases and `libc::c_int` in others. 1.65 is selected as a small bump over 1.64 because it comes with some small "nice" things like workspace-level lints and `cast_mut`. It has been over a year since the last MSRV bump to 1.63 (in 93052d1, "Document the MSRV of the stable channel as 1.63") so we could probably bump higher yet, but there isn't anything else on the list at [1] as useful as `core::ffi`. [1]: rust-lang#4626
@tgross35
tgross35
force-pushed
the
stable-msrv
branch
from
February 13, 2026 07:13
0b6d813 to
8175e4a
Compare
JohnTitor
JohnTitor
approved these changes
Feb 14, 2026
Member
@JohnTitor
JohnTitor
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from me, improvements like #4406 should be unblocked with this 🎉
Amanieu
Amanieu
approved these changes
Feb 14, 2026
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
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.
Perform a small MSRV bump by two versions. The main thing this gets is access to the C types in
core::ffi, which means the ecosystem can start harmonizing around those aliases instead of using e.g.core::ffi::c_intin some cases andlibc::c_intin others.1.65 is selected as a small bump over 1.64 because it comes with some small "nice" things like workspace-level lints and
cast_mut. It has been over a year since the last MSRV bump to 1.63 (in 93052d1, "Document the MSRV of the stable channel as 1.63") so we could probably bump higher yet, but there isn't anything else on the list at 1 as useful ascore::ffi.