Add async execution, structured diagnostics, and distinct platform regressions - #520
Merged
LunaStev merged 1 commit intoSep 8, 2026
Conversation
This was referenced Sep 8, 2026
LunaStev
marked this pull request as ready for review
September 8, 2026 14:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change adds lazy async functions and explicit await suspension, moves additional frontend and backend failures onto structured diagnostics, and replaces selected repeated platform cases with distinct workloads. Ordinary
fun main()drives async work throughstd::task::block_on.The implementation includes backend-neutral resumable frames, a cooperative task executor, readiness integration, a Windows IOCP provider, cancellation acknowledgement, IPv6 async socket helpers, and exact-length reads. Generic method rewriting and typed receiver handling accompany the frontend changes. Explicit MSVC target/linker handling is added while Windows GNU remains available.
Eight existing cases are strengthened and two shared cases are added. They cover bounded streaming search, syntax layouts, architecture-specific aggregate/argument transport, epoll pipe demultiplexing, kqueue-driven parsing, Windows allocation/counting sort, and a FreeBSD bit-graph workload. Earlier platform-matrix cleanup removes the unsubstantiated macOS/iOS/Windows RISC-V cells and records DragonFly amd64 as disabled/planned; it does not claim DragonFly execution support.
Validation and review status:
Closes #516
Closes #517
Closes #518
Closes #519
Related: #362, #395, #397, #398, #399, #409, #435, #437, #439, #440, #441, #442, #443, #444, #445, #292, #498, #515.
Follow-up audit:
Remote CI has now run at this head. Strict Clippy fails on three redundant closures in async lowering; case checking finds reserved
byteidentifiers in two new workloads. The LoongArch workload also exposes the existing arithmetic-index limitation (#436), and native Windows ARM64 still reports the previously tracked access violation (#493). The Windows GNU amd64 case job separately encountered an MSYS2 download timeout; that single transport failure is not being reported as a new compiler defect. These observations do not establish that later blocked steps pass.24 focused follow-up issues were opened after comparing existing reports. Source-only findings are explicitly distinguished from observed remote CI failures in their bodies:
Good first issues: #521, #537, #539, #541, #543, #544.
These follow-ups remain open; they are not additional automatic-closing references.