leetcode

Category	Problems
Sort/search	026, 031, 036, 041, 048, 054, 055, 056, 073, 074, 075, 118, 121, 122, 123, 128, 134, 136, 153, 215, 240, 278
String	005, 006, 008, 010, 014, 028, 038, 043, 044, 127
Numerical	007, 009, 029, 050, 066, 069, 279
Hash/Lookup	001, 003, 012, 013, 020, 030, 049, 076, 187, 349, 350
Stack/Queue/Deque	023, 032, 094, 102, 103, 116, 150
Linked list	002, 019, 021, 024
Two pointers	011, 015, 016, 018, 027, 042, 084, 088, 125, 287
Recursion	004, 025, 033, 034, 035, 045, 079, 098, 101, 104, 105, 108, 111, 124, 130, 301
Backtracking	017, 022, 037, 039, 040, 046, 047, 051, 060, 078
DP	053, 062, 063, 064, 070, 091, 120, 131, 198, 213, 221, 300

Note that binary tree problems are mostly included in the Recursion category.

Environment

《Ubuntu计算机视觉开发环境配置（Python/C++）》《Manjaro计算机视觉开发环境配置（Python/C++）》《Windows配置VSCode+CMake+Ninja+Boost.Test的C++开发环境》

Ubuntu 18.04 / Manjaro 19.0 / Windows 10 / macOS Catalina 10.15.3
Visual Studio Code with following extensions:
- C/C++ (ms-vscode.cpptools)
- C/C++ Clang Command Adapter (mitaki28.vscode-clang) (optional)
- CMake (twxs.cmake)
- CMake Tools (vector-of-bool.cmake-tools)
- CodeLLDB (vadimcn.vscode-lldb) (optional)

sudo snap install --classic code
sudo apt-get install pylint

clang (used by default. You can use other tools as long as your .vscode/c_cpp_properties.json file is modified correctly)

wget -O - http://apt.llvm.org/llvm-snapshot.gpg.key|sudo apt-key add -
sudo apt-get update
sudo apt-get install clang-8 lldb-8

CMake
Boost (for unit testing)

wget -O boost_1_70_0.tar.gz https://dl.bintray.com/boostorg/release/1.70.0/source/boost_1_70_0.tar.gz
tar xzvf boost_1_70_0.tar.gz
cd boost_1_70_0/

sudo apt-get update
sudo apt-get install build-essential g++ python-dev autotools-dev libicu-dev build-essential libbz2-dev libboost-all-dev

./bootstrap.sh --prefix=/usr/
./b2
sudo ./b2 install

Usage

Each folder contains 3 files: solution.hpp, solution.cpp and solution_test.cpp. The first folder 001-Two-Sum contains an additional main.cpp file, in case you don't feel like using unit testing and you can test your own cases in main.cpp.

Add following lines to your settings.json to configure the building and linting:

{
    "clang.executable": "clang++",
    "clang.cflags": ["c11"],
    "clang.cxxflags": ["-std=c++17"],
    "lldb.executable": "lldb"
}

Steps to build a solution:

Change the line set(PROBLEM_NAME {Problem_Folder}) in CMakeLists.txt to choose the problem you want to solve, in which {Problem_Folder} is the folder name of the problem. For example, set(PROBLEM_NAME "001-Two-Sum").
Press Ctrl + Shift + P to bring up the Command Palette of VSCode. Type in CMake, and look for a CMake: Configure command, select it. It will configure the cache files and makefile which are located in build folder by default.
Type in or look for a CMake: Build command in the Command Palette and execute it. It will compile the source codes of the solution that you previously chose.
Debug Press Ctrl + Shift + D or click the bug icon on the left. The .vscode/launch.json for debugging is already set up for you, and both GDB and LLDB is supported.

gdb: Choose (gdb) Launch and you're good to go.

lldb: Choose (lldb) Launch. You may need to disable and re-enable ms-vscode.cpptools and mitaki28.vscode-clang extensions in case the variables won't properly display in "Watch" Panel. Data visualization is supported (https://github.com/vadimcn/vscode-lldb/wiki/Data-visualization).
Unit testing Type in or look for a CMake: Run tests command in the Command Palette and execute it. It will run all test cases in solution_test.cpp. Feel free to add your own test cases.

Clear build folder:

Press Ctrl + Shift + P to bring up the Command Palette. Type in Task: Run Task and press enter. Choose clean will delete everything in the build folder. Bear in mind that you need to configure the project after cleaning the folder or switching to another solution, by either executing Task: Run Task -> configure or CMake: Configure.

ActiveVariable / leetcode

leetcode

Stats

Solutions

Problem categories

Environment

Usage

About

Languages