Specify when NetEvent.fd is valid across readiness backends

未关闭
#1,013 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust

调研方向

Start with std/sys/linux/event.wave:18 and trace NativeEvent production through the public NetEvent facade in net_event_wait. Review the Linux, kqueue, and Windows backends to identify their current fd and token behavior. Completion requires an explicitly agreed portable validity contract, tested rules for every backend, and examples using only fields guaranteed by that contract; implementation should wait for design discussion with @LunaStev.

由索引模型根据 Issue 内容生成。

描述

discussion enhancement help wanted

Motivation

The Linux provider returns fd=-1 while preserving the caller token; kqueue and Windows providers return a descriptor. net_event_wait copies this field into the public NetEvent without a field-validity contract. Portable consumers cannot know whether fd is usable.

Starting point: std/sys/linux/event.wave:18.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Traced NativeEvent production through the public NetEvent facade. Executed compiler probes use the matching checkout-built compiler and std on Linux amd64 (Rust 1.89.0 / LLVM 21.1.8). Source/header or mocked checks are not native execution on another OS.

Scope

Choose a stable token-first/optional-fd or always-valid-fd contract and document the representation without implying native backend parity.

Design discussion required

This issue records a proposal or an unresolved contract; it is not approval to choose new semantics. Please mention @LunaStev to discuss the design before starting implementation.

Completion criteria

  • Every backend has a tested, explicit NetEvent.fd validity rule.
  • Tokens retain full identity and descriptor reuse does not create stale associations.
  • Examples use only fields guaranteed by the portable contract.
主要语言
Rust
星标
56
派生
21
平均合并
23 小时 20 分钟
30 天内合并 PR
45

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

wavefnd/Wave 的其他 Issue

查看 wavefnd/Wave 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。