-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stabilize ip_in_core feature #119276
Stabilize ip_in_core feature #119276
Conversation
r? @m-ou-se (rustbot has picked a reviewer for you, use r? to override) |
I wonder if 1.76 has branched yet? Would be nice to get this into 1.77. |
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.
Thanks!
@bors r+ |
Stabilize ip_in_core feature Finally the last stage of rust-lang/rfcs#2832. Since the FCP was [just completed with disposition *merge*](rust-lang#108443 (comment)), I create the stabilization PR for the `ip_in_core` feature. Allowing usage of `core::net` on stable Rust. The error type `core::net::AddrParseError` itself becomes stable with this PR. However, `core::error::Error` is still unstable, so the `Error` impl for this type is not available on stable rust. Simply because `error_in_core` is not stable yet, but that should be fine!
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e87ccb8): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 670.109s -> 669.342s (-0.11%) |
This is just noise returning back to steady state. |
Finally the last stage of rust-lang/rfcs#2832. Since the FCP was just completed with disposition merge, I create the stabilization PR for the
ip_in_core
feature. Allowing usage ofcore::net
on stable Rust.The error type
core::net::AddrParseError
itself becomes stable with this PR. However,core::error::Error
is still unstable, so theError
impl for this type is not available on stable rust. Simply becauseerror_in_core
is not stable yet, but that should be fine!