Tracking Issue for `alloc::io` and `core::io`

[a1phyr]

Feature gate: #![feature(alloc_io)]

This is a tracking issue for using module io in alloc (and hopefully in core one day).

Public API

For now, alloc::io module. One day, core::io.

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

• ACP (accepted): ACP: Introduce alloc::io libs-team#755
• Implementation:
  • Move OS-dependent parts of std::io to alloc #152918
  • Migrate rest of std::io to alloc #154684
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[Mark-Simulacrum]

In #154654, we noted that core::io is currently gated with the feature gate core_io_borrowed_buf (code).

I would like to propose we stabilize core::io and alloc::io existing while leaving the contents unstable for now. That would avoid users needing to add multiple feature gates, and I think it's highly likely those names will remain in existence (and eventually have contents). Can libs-api approve that, either via FCP or just commenting here (since we're just stabilizing the modules not convinced a 10+ day wait is really needed).

[Amanieu]

We discussed this in the @rust-lang/libs-api meeting. We're not inclined to stabilize these modules before at least one item is stabilized inside them.

If excessive feature gates are a concern, this could be simplified by just having a single core_io feature that covers anything in core::io that is already stable today.