Development of API-based errant_compare #50
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.
Hi, as can be seen in the issue #25, I think API-based errant_compare feature will be useful for many people.
I also want the feature so I created a pilot version.
Mainly,
__eq__()
function to the Edit class to compare two objects easily.Using the GEC system's correction results at hand, I confirmed that the results of the official implementation match the results of my implementation.
I do not think this PR will be merged as is, but I hope this is a clue to development of API-based errant_compare!