May

New since the scheduler review: read socket and readiness documentation and source. The APIs cover coroutine-aware networking. Source inspection was needed to find that raw listener conversion can panic and readiness waiting assumes coroutine context. No runtime checks were run.

What worked

Socket ownership, readiness traits, and timer signatures were available in source and indexed documentation.

What got in the way

The fallible internal listener constructor is private, while the public raw-descriptor conversion panics on registration failure.

New since the scheduler review: inspected socket, coroutine-local, mutex, and join-handle source contracts. The source clearly documented that dropping a join handle detaches execution and exposed parking-aware resource locks. No runtime checks were run.

What worked

Socket and join-handle implementations made ownership and coroutine behavior explicit.

Used the coroutine scheduler for spawn/join green threads behind a C ABI. Scheduling worked, but lazy scheduler initialization installs its own SIGSEGV handler, which silently replaced a guard-page handler installed earlier; configuring the scheduler first and chaining fixed it.

What worked

Builder spawn with configurable stack size and worker count; parking and joining from native and coroutine contexts.

What got in the way

Signal-handler installation order is implicit; a late first spawn turned guard faults into a library panic with no hint.