Move std::io::copy internals to alloc::io

[bushrat011899]

ACP: rust-lang/libs-team#755
Tracking issue: #154046
Split From: #156527
Blocked On: #158547

Description

Moves the generic implementation of std::io::copy to alloc::io. This is effectively a direct cut and paste. Blocked on #158547.

Worth considering is how we may want to expose the generic copy function for end users. Currently, std only exposes std::io::copy, which internally uses kernel_copy and falls back onto generic_copy as required. We could expose generic_copy as alloc::io::copy, but then alloc::io::copy and std::io::copy would be different functions. There are instances where that already happens (core::panic! is not the same as std::panic! for example), but this would be an easy mistake to make with performance implications.

Alternatively, EII could allow the kernel_copy function to be provided to alloc, so the full copy function is defined in alloc::io and then reexported in std::io. But that's dependent on EII being more stable.

For now, this PR just moves generic_copy to signal that the full std::io::copy is very close to being able to be moved into alloc::io.

---

Notes

• No AI tooling of any kind was used during the creation of this PR.
• Please see Tracking Issue for alloc::io and core::io #154046 (comment) for a review order and broader context for this PR.

[rustbot]

r? @clarfonthey

rustbot has assigned @clarfonthey.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: @ChrisDenton, libs
• @ChrisDenton, libs expanded to 13 candidates
• Random selection from 6 candidates

[bushrat011899]

@rustbot blocked