Use Darwin and FreeBSD overflow errno values for synthetic std errors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- operating-systems
Research direction
Read std/sys/errors.wave starting at line 12 to find the target-selected SYS_ERR_OVERFLOW constants for Darwin and FreeBSD. Update only the affected values so both synthesize -84, while Linux, Windows, and WASI remain unchanged. Confirm the target-selection providers and the checked sleep/duration overflow regression, then use native CI for macOS and FreeBSD.
Written by the indexing model from the issue text.
Description
Problem
SYS_ERR_OVERFLOW is -75 on both macOS and FreeBSD, while their errno headers define EOVERFLOW as 84. Checked time/sleep helpers therefore synthesize an error in the Linux domain on those targets. Windows normalization is intentional and separate.
Starting point: std/sys/errors.wave:12.
Validation
Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Source-to-official-header comparison; no native Darwin/FreeBSD run. 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.
Header references: XNU errno.h, FreeBSD 14.4 errno.h.
Scope
Correct only the affected target-selected constants and their observable synthetic results. Preserve Linux, Windows and WASI conventions.
Related: #945. These links do not claim those broader or completed scopes are unfinished.
Completion criteria
- macOS and FreeBSD synthetic overflow returns -84.
- Target-selection tests cover both affected providers and unchanged other targets.
- Checked sleep/duration overflow regression and native CI confirm the result.
This is a bounded, unassigned task with the starting point and focused checks above. Keep unrelated refactoring out of the change.
- Dominant language
- Rust
- Stars
- 56
- Forks
- 21
- Avg merge
- 7h 19m
- Merged PRs (30d)
- 61
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wavefnd/Wave
-
Validate CI command vectors before indexing Cargo subcommandsPossibly taken @amandeavor claimed this today. Openbug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
build good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
discussion enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
manuscript-lang/manuscript#1364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fable-compiler/Fable#5157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
C-bug needs-triage O-UEFI T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
移动端宽屏适配Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day