You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: leetcode/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ All LeetCode problems can be found [**here**](https://leetcode.com/problemset/al
24
24
If you have a solution to any of these problems (which are not being **repeated**, that's great! Here are the steps:
25
25
26
26
1. Add a new file in `leetcode/src` with the number of the problem.
27
-
- For example: if the problem's number is 98, the filename should be `98.cpp`.
27
+
- For example: if the problem's number is 98, the filename should be `98.cpp`.
28
28
2. Provide a small description of the solution at the top of the file. A function should go below that. For example:
29
29
30
30
```c
@@ -37,7 +37,7 @@ If you have a solution to any of these problems (which are not being **repeated*
37
37
38
38
3. Do not provide a `main` function. Use the required standalone functions instead.
39
39
4. Doxygen documentation isn't used in LeetCode solutions. Simple/small documentation or comments should be fine.
40
-
5.Don't include libraries/headers such as `iostream`. Your file should be the solution to the problem only.
40
+
5.Please include dependency libraries/headers such as `<iostream>`, `<vector>` along with the `Solution` class to the problem. This will help the CI to succeed without the dependency errors.
41
41
42
42
> **Note**
43
43
> There was a requirement to update the `leetcode/DIRECTORY.md` file with details of the solved problem. It's not required anymore. The information about the problem is fetched automatically throughout the LeetCode API.
0 commit comments