Per operating system seam

未关闭
  • 哪里不对？
#3 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
46/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
operating-systems

调研方向

Start by reading the src/sys backend and the shared code that currently makes Windows calls; the issue does not name specific files or tests. Trace Windows-only features such as exception approval, the extension server, and the contain role, then identify how the tests are split between shared behavior and platform behavior. Done means the Windows suite and battery pass unchanged, Windows targets check with zero warnings, and a target with no backend stops only at the backend refusal.

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

描述

roadmap

Move every Windows call behind src/sys so shared code reaches the backend only through crate::sys, and split the tests into shared behaviour tests and per platform tests. Windows-only features (approval of an exception, the extension server, the contain role) stay behind cfg(windows).

Done when: the Windows suite and battery pass unchanged, the Windows targets check with zero warnings, and a target with no backend stops only at the backend refusal.

主要语言
Rust
星标
0
派生
0
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

WikdSolvemProbler/process-tree-guard 的其他 Issue

查看 WikdSolvemProbler/process-tree-guard 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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