Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Use Darwin and FreeBSD overflow errno values for synthetic std errors

Open Beginner friendly
#1,005 0 comments 0 reactions 0 assignees View on GitHub

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

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

bug good first issue

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

  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 wavefnd/Wave

All issues in wavefnd/Wave

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.