Why list.List?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue questions the use of Go's list.List in the ordered map implementation but names no files, tests, or concrete replacement. First inspect the implementation and its performance rationale; the work is not ready until a specific change and acceptance criteria are agreed.
Written by the indexing model from the issue text.
Description
If you wanted to build “high performance” thing, then why you didn’t implement list by hands? Why you decided to pay overhead of list.Element?
- Dominant language
- Go
- Stars
- 1k
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 elliotchance/orderedmap
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
elliotchance/orderedmap#60 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
elliotchance/orderedmap#59 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
elliotchance/orderedmap#58 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
elliotchance/orderedmap#56 · 1 comment · 3 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
elliotchance/orderedmap#55 · 3 comments ·
All issues in elliotchance/orderedmap
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100