ltlopes#15
Open
ltlopes 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
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/<github_username>.py.Approach Description
Producer–consumer with a single scheduler thread.
Workers (ThreadPoolExecutor) only run target.build(...) and push (name, result) onto a SimpleQueue.
Main thread is the only scheduler: drains the queue, decrements in_degree, submits newly-ready targets.
No locks on the hot path — in_degree, results, and dependents are touched only by the main thread; the queue handles cross-thread handoff.
Fast path: If the graph is a pure chain (1 root, every node has ≤1 dep), skip the pool and build in-line. Avoids thousands of thread dispatches.