Simple delimiter support #28
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
We aren't using these definitions anyway.
ForNeVeR
force-pushed
the
feature/14-delimiters
branch
from
3d0a9b2
to
b227f03
Compare
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.
I've added the support for some of the delimiter types mentioned in #14.
Fortunately, it turned out that the render already supports this feature. Here's the screenshot (check the big braces inside of the sum operator):
Remaining issues:
\left.and\right.aren't supported (tracked in Extensible delimiters (\left and \right) #14)refparameters (tracked in Remove usage of ref parameters from the parser #29)The implementation is yet very ad-hoc and maybe is missing very much important details; we'll need to determine and fix these later.