Per operating system seam

Open
  • Is something wrong?
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
46/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
operating-systems

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Rust
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

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.

More from WikdSolvemProbler/process-tree-guard

All issues in WikdSolvemProbler/process-tree-guard

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.