-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Tracking Issue for ip_in_core #108443
Comments
I guess there's nothing left to do. |
Can this be stabilized before |
I believe so.
https://github.com/faern/rust/blob/1291216ac986ccc1432bf0bf2db9545e5251dd24/library/core/src/net/ip_addr.rs
|
You can't feature gate a trait implementation. The question would be if it's possible to refer to any of the |
Thanks for the explanation @Nemo157 and yes, I agree that it can't be stabilised before Error then. |
I disagree, this feature can be specialized before This is just like all existing errors in rust/library/core/src/error.rs Lines 1046 to 1052 in 735bb7e
|
Ping @rust-lang/libs-api, could this go into FCP? |
Yes, please. |
This comment was marked as resolved.
This comment was marked as resolved.
@rust-lang/libs maybe? Would like to get some confirmation that this is on some list somewhere for discussion. |
I've added the nomination label so it'll be discussed in a libs-api meeting, though it's possible a libs-api member may decide to remove the label and just fcp it. It'd likely be helpful if someone could provide a summary of the current state of things and why this is ready for stabilization. |
I'm not claiming this bears enough weight to stabilize but I just allowed |
Starting FCP for stabilization. @rfcbot merge |
Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
I pushed a stabilization PR: #119276 |
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!
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!
Feature gate:
#![feature(ip_in_core)]
This is a tracking issue for RFC rust-lang/rfcs#2832, providing networking types in
core::net
:IpAddr
,Ipv4Addr
,Ipv6Addr
,SocketAddr
,SocketAddrV4
,SocketAddrV6
,Ipv6MulticastScope
andAddrParseError
.Steps / History
core
#104265Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
The text was updated successfully, but these errors were encountered: