optimization check for ParseCheckConstraints #4063
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
|
This failure may be a problem with the unit test writing. |
mittwillson
pushed a commit
to itering/gorm
that referenced
this pull request
Sep 27, 2021
cgxxv
pushed a commit
to cgxxv/gorm
that referenced
this pull request
Mar 25, 2022
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.
ParseCheckConstraints func
match English letters and midline
Here, the regularity of matching English characters and midline does not have to be a regular compilation operation every time. At the bottom of go reg, the logic here is also consumed. For details, see the implementation of compile and compile of the bottom source code of go reg.