swiftwasm / swiftwasm/JavaScriptKit
Respect Job priority in WebWorkerTaskExecutor
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 986
- Forks
- 76
- Avg merge
- 21h 11m
- Merged PRs (30d)
- 4
Description
Currently, WebWorkerTaskExecutor doesn't re-order jobs based on their priorities, but just schedules them in the order they are enqueued.
Contributor guide
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.
Research direction
Start by locating the WebWorkerTaskExecutor entry point and its job enqueueing and scheduling logic. Verify how job priorities are represented, then ensure queued jobs are selected by priority rather than enqueue order; done means higher-priority jobs run first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, swift, wasm
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100