Repository navigation
TeX reader: accept empty delimiters in \genfrac - #300
Merged
Merged
Conversation
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
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.
\genfrac{}{}{0pt}{}{a}{b}currently fails because the delimiter parser consumes the closing}of an empty argument.I reused one delimiter parser for both arguments and left an unescaped
}for the surrounding braces parser. This allows either delimiter to be empty while preserving escaped and unbraced delimiters.The regression covers both empty delimiters, either side empty, lineless/normal/display fractions, and unbraced nonempty delimiters.
Validation (GHC 9.10.3):
cabal test --test-show-details=directfails onlygenfrac-empty(1 of 3160 tests).