More efficient resolution of joiner contexts#172
Merged
Conversation
In some pathological cases, this would out eligibility under CONTEXTJ rules much faster.
|
@kjd Is there a plan to backport this fix to the |
Owner
Author
|
No plan unless there is an identified need. The Python 2 interpreter ended security fixes on 1 January 2020 so I am not sure if it makes sense to prolong that branch now over 4 years later. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In some pathological cases, this would out eligibility under CONTEXTJ rules much faster.