Skip to content

Conversation

@goblineer
Copy link

No description provided.

@aphunk
Copy link

aphunk commented Mar 5, 2019

Nice job! Our approach is very similar. I realized after I submitted it that it can be a lot less verbose, but this makes a lot of sense when using the test results to solve the problem.

@ace-n
Copy link

ace-n commented Apr 21, 2019

FYI: ask a TA about using git push --force, which should (hopefully) solve the merge issues.

Warning: be very careful with this command, as it can permanently delete git history. (It's pretty much the most dangerous git command there is 😨- but is largely harmless once you know how to use it. 🙂)

Copy link

@ace-n ace-n left a comment

Choose a reason for hiding this comment

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

(Was able to find your code here.)

LGTM other than a style nit or two. 👍 Can you add complexity analysis as well? 🙂

raise NotImplementedError
end
i = 0
if (array1 == nil) && (array2 == nil)
Copy link

Choose a reason for hiding this comment

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

Nit: these if statements are a bit redundant - how about combining some of them, e.g:

if (array1 == nil && array2 == nil) {
  return true;
} elsif (array1 == nil || array2 == nil) {
  return false;
}
...

return false
elsif array1.length != array2.length
return false
else
Copy link

Choose a reason for hiding this comment

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

Tiny nit: the else is redundant here. You can move this inner block out of it. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants