vnaonlu / leetcode-daily

a project including my leetcode solutions with unittests, which are written in c++.

LeetCode Daily in C++

This repository collects some of my LeetCode solutions in C++ for free questions since 2021/09/06. The remain questions is still being solved so the current project may not contain the solutions you are looking for. Please check the chapter Getting Started for more details.

Here is my LeetCode account if you are interested.

Getting Started

See Activity to check the recent solution resolution status, including the historical statistics and the recent submissions. All solved solutions are stored in src and more information can be found at Find Solution. See Installation if you are interested in how to build the project or add some testcases for some solutions.

More information about solved solution can be found at docs/solved_solutions.md and unsolved questions can be found at docs/unsolved_solutions.md.

Activity

More information about full activities can be found at:

• All submissions in 2024: docs/2024.md
• All submissions in 2023: docs/2023.md
• All submissions in 2022: docs/2022.md
• All submissions in 2021: docs/2021.md

Finding Solution

All solved solution information can be found at docs/solved_solutions.md and all solutions are in the directory of src corresponding to their LeetCode frontend ID. For instance, the solution for 1. Two Sum is stored in src/q_1_50/q0001.cc. In addition, the solution fragment always appear between LEETCODE_BEGIN_RESOLVING and LEETCODE_END_RESOLVING, e.g.

// ...
LEETCODE_BEGIN_RESOLVING(1, TwoSum, Solution);

class Solution {
public:
  vector<int> twoSum(vector<int> &nums, int target) {
    auto memo = unordered_map<int, int>();
    for (int i = 0; i < nums.size(); ++i) {
      auto find = memo.find(target - nums[i]);
      if (find != memo.end()) {
        return vector<int>{find->second, i};
      }
      memo.emplace(nums[i], i);
    }
    return vector<int>{-1, -1};
  }
};

LEETCODE_END_RESOLVING(Solution);
// ...

Or you can simply use the script ldt to cat the specific solution via:

# in the project root
$ ./ldt cat <question id>

But the script probably won't work as it is very rough currently.

Installation

It is not necessary to build or install this project if you just want to find specific solutions, but you can still build and run this project. There has a script named ldt in the root, which is a tool to automatically add/delete the solution in this project, generate the solution template or update the readme or log. However the script may too rough to use since I haven't tested it in other environment.

Before running to build project, please check below dependencies:

• C++20 supported Compiler.
• CMake above 3.20.

Then you can build the project manually by

$ git clone https://github.com/vNaonLu/leetcode-daily.git
$ cd leetcode-daily
$ cmake -S . -B build -DENABLE_LEETCODE_TEST=ON
$ cmake --build build
# Run the unittests
$ ./build/leetcode_test

leetcode-daily's Issues

repo_manager.py crashed when add question 160

Incorrect format of empty vector container

Found issue when adding question #78

// the first element is incorrect
vector<vector<int>> exp = {[], {1}, {2}, {1, 2}, {3}, {1, 3}, {2, 3}, {1, 2, 3}};

Support the template of the struct type solution and its test case

Such as Question #707

Wrong initializer_list elements with char type which is generated by leetcode_add.py

Found issue when adding question #130

the generated template unittest:

vector<vector<char>> board = {{"X", "X", "X", "X"}, {"X", "O", "O", "X"}, {"X", "X", "O", "X"}, {"X", "O", "X", "X"}};

which can not initialize the char type by ".

Wrong unit test template generated when the type of solution function is void.

Found issue when adding question #130

template generated by leetcode_add.py:

// since the solution function with void return type
void solve(vector<vector<char>>& board) {}

// then the pytool generates an ambiguous variable.
void exp = [["X","X","X","X"],["X","X","X","X"],["X","X","X","X"],["X","O","X","X"]];

Wrong argument type generated

Found the issue with Question #174

//actual
  vector<int> dungeon = {-2, -3, 3, -5, -10, 1, 10, 30, -5};

//expect
  vector<vector<int>> dungeon = {{-2, -3, 3}, {-5, -10, 1}, {10, 30, -5}};

The wrong number of test cases was generated by leetcode_add.py.

Found the issue with Question #47

The unittest template generates only one case.

The wrong number of test cases was generated by leetcode_add.py.

Found issue when adding question #43

the tool generated only one sample example but Question #43 has two sample cases.

LDT: merge message.

A merged message from devel/daily to main is need.
I am considering the following format:

adds the {count} solution(s) in week{week}.
add solutions details:
  * {rev} adds q{id} with TC O({tc}) and SC O({sc}).
  * {rev} adds q{id}.
  * {rev} adds q{id} with TC O({tc}) and SC O({sc}) where {note}.

The string in test cases is not define if the value is "".

Found the issue in Question #17

TEST(q17, sample_input02) {
  l17::Solution solver;
  // miss this-> string digits = "";
  vector<string> exp = {};
  // Try EXPECT_EQ_ANY_ORDER_RECURSIVE
  // if the element is also matched in any order.
  EXPECT_EQ_ANY_ORDER(solver.letterCombinations(digits), exp);
}

Question 79 does not generate the test case.

Generate binary trees more efficiently and more readable.

For Example

[4,-7,-3,null,null,-9,-3,9,-7,-4,null,6,null,-6,-6,null,null,0,6,5,null,9,null,null,-1,-4,null,null,null,-2]

Dummy listnode released then the answer has been released too

Found the issue with Question #2

Solution: complete the complexity information about solutions.

The current complexities information is incomplete.

This card ignores the complexity about Strcutured Solutions.

Equal test function supports the match in some condition.

The answer to some questions such as #922 is accepted in multiple answers.

For example:

Input: nums = [4,2,5,7]
Output: [4,5,2,7]
Explanation: [4,7,2,5], [2,5,4,7], [2,7,4,5] would also have been accepted.

Wrong test case parsing with question 463

TEST(q463, sample_input01) {
  l463::Solution solver;
  vector<vector<int>> grid = {};
  //0 = 0
  //1 = 1
  //1 = 0
  //0 = 1
  //0 = 0
  //1 = 1
  //0 = 0
  int exp = 16;
  EXPECT_EQ(solver.islandPerimeter(grid), exp);
}

The expected answer doesn't match the actual answer due to the meaning of the question is in any order.

Found issue when adding question #49

// the return answer in the sample case 1 is
vector<vector<string>> exp = {{"bat"}, {"eat", "tea", "ate"}, {"tan", "nat"}};

// the expected answer generated by the tool is
vector<vector<string>> exp = {{"bat"}, {"nat", "tan"}, {"ate", "eat", "tea"}};

No Unit test case is generated in question #929.

Found the issue with Question #929

The unittest template does not generate any test case.

Nested html tag crashes question.py

Found the issue in Question #852

Approximately equal with double

Found the issue question id 50

temporary solution

inline bool approximately_equal(double x, double y) noexcept {
  return abs(y - x) < 1e-6;
}