Don't be as strict about solution delimeters #614
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Less code, more power! Win win! Thanks... look forward to trying this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #551 and fixes #422
I didn't explicitly include fuzzy string checking for #422 but that's because the delimeters are actually pretty close, so this is difficult to do -- for example, "BEGIN SOLUTION" and "END SOLUTION" actually share a large amount of text because of the "SOLUTION" part. But, I think being able to be flexible about everything else (e.g. comment marks) will still be sufficient for that.
cc @dsblank