-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
Added Longest Common Subsequence in Java & C++ #1587
Conversation
This is the code for Longest common sub-sequence.
This is code for Longest Common Sub-Sequence, in java language.
This is Longest Common Sub-Sequence code in java language.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but they currently aren't being tested: https://travis-ci.com/TheRenegadeCoder/sample-programs/jobs/245039381#L562-L581
I think that's because we use "lcs" for the file names. It's a bad abbreviation, but it's what we use. You'll have to update your files accordingly for the testing to trigger.
Formated the indentation, and name of file updated from longest-common-subsequence to lcs.
Updated the name of file from longest-common-subsequence to lcs
Corrected the link for longest-common-subsequence.
Done the changes, you requested. |
Corrected some piece of code
Corrected some piece of code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. That's the last bug I believe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! I think these are good to go now.
Congrats on taking the first step to contributing to the Sample Programs repository maintained by The Renegade Coder! For simplicity, please make sure that your pull request includes one and only one contribution.
Complete the Applicable Sections Below
Find which section best describes your pull request and make sure you fill it out. To start, let us know which issue you've fixed.
Code Snippets
Added/Updated <Sample Program> in <Language>
formatDocumentation
Added/Updated <Sample Program> in <Language> Article
formatTesting
Added/Updated <Language>/<Project> Testing
formatNotes
Feel free to describe what you added or updated.