Investigate performance of delegating `yield` in tree traversals
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, python, typescript
- Domain
- performance
Research direction
The issue names no files, tests, or entry points; begin by locating the tree traversal implementations that manage their own stacks. Benchmark those versions against recursive traversal using TypeScript yield*, Python yield from, and Java Stream.concat, then report whether performance is comparable and which implementation should be preferred.
Written by the indexing model from the issue text.
Description
It would be really cool if we could use yield* (TypeScript) and yield from (Python) or perhaps even Stream.concat (Java) in the tree traversal goodies to write the traversals recursively -- the code would read very naturally. However, I'm not sure about the performance implications of doing so.
Let's investigate the performance of these relative to the implementations that manage their own stack. If the recursive implementation is comparable in performance, then I think it should win on the grounds of the code being much nicer.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
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.
More from code-chronicles-code/leetcode-curriculum
-
enhancement kotlin
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
good first issue tests
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
good first issue tests
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
good first issue tests
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
code-chronicles-code/leetcode-curriculum#418 · 1 comment ·
All issues in code-chronicles-code/leetcode-curriculum
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·