Write panics; read returns Result
Platform spec ADR
Write panics; read returns Result
Spec standingStandard
- Contracts and edge cases MUST rules for standard stream reads, writes, and error handling.
- Design model Stream module boundaries and syscall descriptor model for standard I/O.
- Examples Standard stream read and write usage patterns.
- Flow and algorithm Read and write algorithms for standard stream helpers.
- Verification and traceability Runtime syscall and corelib anchors for standard stream I/O.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”v1 write helpers are infallible at the type level; read paths need explicit error handling.
Decision
Section titled “Decision”| Rule | Detail |
|---|---|
| Write | Write / WriteLine must panic on WriteWith failure |
| Read | Read / ReadLine return `Result<string, SyscallError>` |
Consequences
Section titled “Consequences”Diagnostics for write failures use fixed panic strings; callers cannot catch write errors in Beskid v1.
Verification anchors
Section titled “Verification anchors”Corelib stream tests; syscall integration in beskid_runtime.