Optimize scc as hard as possible
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- haskell
- Domain
- data, performance
Research direction
Start by locating the Data.Graph implementation of scc and reviewing how GHC uses it. Establish a benchmark or other performance criterion before proposing changes; done would mean a measured optimization without breaking the existing behavior.
Written by the indexing model from the issue text.
Description
I don't know what can be done here, but GHC uses it, and that makes it a top Data.Graph priority.
- Dominant language
- Haskell
- Stars
- 356
- Forks
- 195
- Avg merge
- 3d 42m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 haskell/containers
-
major-release strictness Tree
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
haskell/containers#1260 ·
-
Map performance Set
Difficulty 5/5 Over a week Newbie friendliness 35/100
haskell/containers#1263 · 4 comments ·
-
low-hanging-fruit performance Seq
Difficulty 4/5 3-5 days Newbie friendliness 43/100
haskell/containers#1262 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
haskell/containers#1261 · 11 comments ·
-
IntSet low-hanging-fruit performance
Difficulty 3/5 1-2 days Newbie friendliness 58/100
haskell/containers#1251 ·
All issues in haskell/containers
Similar issues
-
A `--symbolic` entry binding `𝑛3` and `!n3` passes the load check, since `once` compares spellings, and fails mid-run with a `user error`Possibly taken @sherenkov claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
objectionary/phino#1929 · 1 comment ·
Maintainers usually reply within 1 day
-
CJK text is italicizedPossibly taken @daniel-gregg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
simplex-chat/simplex-chat#7714 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days