rust-lang / rust-lang/rust

Tracking Issue for Borrowed{Fd,Handle} view types

Open
#160,402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-unimplemented T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(fd_view)]

This is a tracking issue for turning &BorrowedFd and &BorrowedHandle into &File and similar.

Public API
impl std::os::fd::BorrowedFd {
    pub fn to_view<T>(&self) -> &T where Self: AsRef<T>;
}

impl AsRef<File> for BorrowedFd {}
impl AsRef<TcpStream> for BorrowedFd {}
impl AsRef<TcpListener> for BorrowedFd {}
impl AsRef<UdpSocket> for BorrowedFd {}
impl AsRef<UnixDatagram> for BorrowedFd {}
impl AsRef<UnixListener> for BorrowedFd {}
impl AsRef<UnixStream> for BorrowedFd {}
impl AsRef<PipeReader> for BorrowedFd {}
impl AsRef<PipeWriter> for BorrowedFd {}
// ... TBD


impl std::os::windows::io::BorrowedHandle {
    pub fn to_view<T>(&self) -> &T where Self: AsRef<T>;
}

impl AsRef<File> for BorrowedHandle {}
impl AsRef<PipeReader> for BorrowedHandle {}
impl AsRef<PipeWriter> for BorrowedHandle {}
// ... TBD


Steps / History

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

Unresolved Questions
  • None yet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the proposed public API for BorrowedFd and BorrowedHandle and review implementation PR #160404. The tracking work is complete only after unresolved questions are addressed, the final comment period finishes, and a stabilization PR is opened.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.