add submission#16
Open
swap357 wants to merge 1 commit into
Open
Conversation
Contributor
✅ Results
Per-graph results
|
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
1 participant
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.
Submission Checklist
submissions/swap357.py.Approach Description
worker pool over a lock-free ready queue.
spin-poll instead of blocking. Workers retry
popleft()onIndexErrorrather than blocking on aqueue.SimpleQueue.Chain serial fast-path. A one-time Kahn-style pre-pass computes the max layer width.
Tradeoffs-
Dict-keyed bookkeeping: arrivals and dependents are keyed by str name rather than int index.
No explicit locks on results: relies on the deque's internal mutex for happens-before