Code Transpilation to Go (Help Wanted)

[Reanon]

We need your help translating the code to Go.

Please check the contribution guidelines at #15

TODO List

• Computational Complexity
• • Time Complexity time complexity using go #99 (@msk397)
• • Space Complexity Add the Go code to space complexity docs #119 (@Cathay-Chen)
• • Space Time Tradeoff feat(time-complexity): code implemented in Go #102 (@Cathay-Chen)
• • Leetcode Two Sum feat(computational_complexity/two_sum): add go code #8 (@Reanon)
• Array And LinkedList
• • Array Add golang code for the array #178 (@guowei-gong)
• • LinkedList Add the Go code to array and linked_list docs (Chapter of Array and LinkedList) #188 (@Cathay-Chen)
• • List List using Go #128 (@msk397)
• Stack And Queue
• • Stack feat(stack_and_queue): add go code. #45 (@Reanon)
• • Queue feat(stack_and_queue): add go code. #45 (@Reanon)
• • Deque feat(stack_and_queue): add go code. #45 (@Reanon)
• Hashing
• • Hash Map Add C++, Python, Go code for chapter_hashing #110 (@msk397)
• • Hash Collision
• Tree
• • Binary Tree feat(pkg): support go basic pkg #20 (@Reanon)
• • Binary Tree Types feat(tree): add go code #29 (@Reanon)
• • Binary Search Tree feat(tree): add go code #29 (@Reanon)
• • AVL Tree feat(tree/avl_tree): add go code #224 (@Reanon)
• Heap
• • Max Heap feat(heap): add go codes #246 (@Reanon)
• Searching
• • Linear Search feat(pkg): support go basic pkg #20 (@Reanon)
• • Binary Search binary_search using go #76 (@Slone123c )
• • Hash Search Hashing search and test using go #96 (@Slone123c)
• Sorting
• • Bubble Sort Bubble sort using go #80 (@Slone123c)
• • Insertion Sort Insertion sort using go #92 (@msk397)
• • Quick Sort Quick sort using go #94 (@msk397 )
• • Merge Sort time complexity using go #99 (@msk397 )
• Basic Pkg
• • List Node feat(pkg): support go basic pkg #20 (@Reanon)
• • Tree Node feat(pkg): support go basic pkg #20 (@Reanon)
• • Print Utils feat(pkg): support go basic pkg #20 (@Reanon @krahets)

Commit Guidelines

1、Format of the commit message
Refer to AngularJS Git Commit Message Conventions

<type>(<scope>): <subject>

Allowed <type>

• feat: feature, complete a part of the code.
• test: testcase.
• fix: fix some bugs.
• docs: documentation, complete a part of the doc.
• style: formatting, …

Allowed <scope>

• chapter_name/module_name

For example, if you complete the go code of linkedlist_queue in chapter_stack_and_queue, the commit message should be like：

feat(stack_and_queue/linkedlist_queue): add go code.

2、What one commit contains
If you complete two module code, testcase and docs, you commit log should be like:

docs(tree/binary_tree_bfs): add go code.
docs(stack_and_queue): add go code.
feat(stack_and_queue/linkedlist_queue): add go code and testcases.
test(tree/binary_tree_bfs): add go testcases.
feat(tree/binary_tree_bfs): add go code.

If you fix a bug, the commit log should be like :

docs(searching/linear_search): modify go code.
fix(searching/linear_search): fix go code.

Code Style

1、All code should be error-free when run through gofmt and go test.
2、Consistent with existing go code style.
3、Refer to uber/go-style.

[krahets]

Hello @itsarraj . Thank you! How can we help you?

[ddkwork]

can add ntree？

[krahets]

Closed because the 1st edition has been completed! Thank you for the great work!