Repository navigation
Design for a Worker class on top of Thread and Atomics - #78
Merged
Merged
Conversation
docs/worker-design.md: the Web Worker API shape (postMessage, onmessage, onerror, close, terminate) over Thread.spawn and Atomics.wait / notify, with dispatch / receive / join standing in for the event loop tslang does not have. Messages are handed over, not copied; terminate stops the worker between handlers. Lists what -mm=own has to be checked for first, the order of work and the tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What
Adds
docs/worker-design.md: a design for an MDN-styleWorkerin the defaultlib, built onThread.spawn/join,Atomics.wait/notifyandShared<T>, which are already onmain. This PR has no code, only the design.Summary of the design
new Worker<In, Out>((self) => { self.onmessage = ...; }). The worker's code is a function, since there is no script URL to load. It has typedpostMessagein both directions, plusonmessage,onerror,close()andterminate().dispatch(timeout),receive()orjoin().JSON.stringifygives a real copy.terminate()stops the worker between handlers rather than killing the thread, and drops queued messages in both directions.Atomics) so queued messages stay visible to the collector (gc) and keep their counts (rc). If that can't work underown, it falls back to a C++ queue.For reviewers
-mm=own: can objects go in the queue, and doespostMessagemove its argument or only borrow it? The first step of the work plan is a queue test with class instances, so this gets settled before anything is built on top.MessageChannel,addEventListenerandwaitAsync.mainreturns. The README will say so; nothing enforces it.🤖 Generated with Claude Code