Optimize Dijkstra’s Algorithm Implementation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No file, test, or entry point is named. Locate the current Dijkstra implementation and read how it finds shortest paths before reviewing the suggested priority-queue optimization. Done means the implementation is optimized as agreed and its existing behavior remains correct.
Written by the indexing model from the issue text.
Description
Description: Review the current implementation of Dijkstra’s algorithm for finding the shortest path in a graph. Identify areas for optimization, such as using a priority queue.
- Dominant language
- Java
- Stars
- 3
- Forks
- 0
- 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 Mmabiaa/Data-Structure-And-Algorithms-Java
-
bug help wanted
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
documentation enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
documentation enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
bug enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
documentation enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Mmabiaa/Data-Structure-And-Algorithms-Java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100