Skip to content

refactor: change List<Integer> to LinkedList<Integer> and remove 'n < 0' #5439

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.

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

Closed
wants to merge 1 commit into from

Conversation

xizhengl
Copy link

@xizhengl xizhengl commented Aug 31, 2024

  • change List to LinkedList and remove 'n < 0'

@codecov-commenter
Copy link

codecov-commenter commented Aug 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 50.98%. Comparing base (b396a97) to head (54175da).
Report is 3 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5439      +/-   ##
============================================
+ Coverage     50.97%   50.98%   +0.01%     
+ Complexity     3159     3158       -1     
============================================
  Files           523      523              
  Lines         15104    15104              
  Branches       2874     2874              
============================================
+ Hits           7699     7701       +2     
+ Misses         7084     7083       -1     
+ Partials        321      320       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -18,16 +19,16 @@ private ArrayCombination() {
* @return A list of all combinations of length k.
*/
public static List<List<Integer>> combination(int n, int k) {
if (n < 0 || k < 0 || k > n) {
if (k < 0 || k > n) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The n < 0 check is important because it ensures that the input values are valid within the context of combinations, prevents undefined behavior.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like if you remove this check everything will work correctly. And you're right, we can remove it. But this check provides readable constraints and with this check the code becomes more readable.

return combinations;
}

private static void combine(List<List<Integer>> combinations, List<Integer> current, int start, int n, int k) {
private static void combine(List<List<Integer>> combinations, LinkedList<Integer> current, int start, int n, int k) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using LinkedList instead of List in method parameters is considered bad practice as it provides tight coupling, and issues with extensibility.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

List doesn't seem to have a removeLast method

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has. In code below, you can see that it already used. And code compile and pass tests.

Copy link

github-actions bot commented Oct 7, 2024

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution!

@github-actions github-actions bot added the stale label Oct 7, 2024
Copy link

Please reopen this pull request once you have made the required changes. If you need help, feel free to ask in our Discord server or ping one of the maintainers here. Thank you for your contribution!

@github-actions github-actions bot closed this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants