Skip to content

Document LeetCode solution conventions #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eselyavka merged 1 commit into from
Mar 31, 2026
Merged

Document LeetCode solution conventions #67

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,13 @@ The actively maintained root modules live under `src/`:
- `practice/algorithms/`: standalone coding exercises
- `practice/leetcode/`: LeetCode solutions archive

LeetCode additions follow a lightweight convention:

- place each solution in the matching hundred-bucket package using `solution_<problem_id>.py`
- keep the solution self-contained and include a small `unittest` case in the same file
- prefer the simplest efficient implementation before opening a PR
- use commit titles like `Add LeetCode solution <problem_id>`

## Archive

- `archive/`: archived scripts and reference files kept outside the active code paths
Expand Down
Loading