[[TOC]]
prettier
(used to format the README in the pre-commit hook)
To ensure that the README table is automatically updated with new Solutions, follow these steps to set up a pre-commit hook:
git clone https://gitlab.com/euchangxian/leetcode.git
cd leetcode
bash setup_hook.sh
Contains LeetCode Solutions written in different languages for ME to reference and track my progress.
Started with Go, but Go as an interview language to solve LeetCode questions is a poor choice, since Go's standard library is sorely lacking common data structures and/or algorithms.
Also, solving string/char questions in Go was painful due to runes and such.
Though, Go is still my favorite language by far for Software Engineering due to its ease of use and comprehensive standard library.
Tried Rust for the fun of it. Enjoyed it. Too time-consuming to deal with the borrow-checker when solving Graph questions. Though I would want to engineer some software with it some time in the future.
Now solving in C++. Like it.
-
Rust solutions are not run-able. Rust requires a different sort of directory that is not really compatible with the way this Repository is structured.
-
Code Coverage Badge showing
unknown
. This is a known issue with GitLab Child Pipelines. I could technically not use child pipelines, but for clean-code/configuration purposes, I would rather separate the concerns of each pipeline. Not knowing the test coverage is fine. This repository is not a Library.