enum FileCheckDiag::MatchType
Description
What type of match result does this diagnostic describe? A directive's supplied pattern is said to be either expected or excluded depending on whether the pattern must have or must not have a match in order for the directive to succeed. For example, a CHECK directive's pattern is expected, and a CHECK-NOT directive's pattern is excluded. All match result types whose names end with "Excluded" are for excluded patterns, and all others are for expected patterns. There might be more than one match result for a single pattern. For example, there might be several discarded matches (MatchFoundButDiscarded) before either a good match (MatchFoundAndExpected) or a failure to match (MatchNoneButExpected), and there might be a fuzzy match (MatchFuzzy) after the latter.
Declared at: llvm/include/llvm/Support/FileCheck.h:105
Enumerators
| Name | Value | Comment |
|---|---|---|
| MatchFoundAndExpected | 0 | Indicates a good match for an expected pattern. |
| MatchFoundButExcluded | 1 | Indicates a match for an excluded pattern. |
| MatchFoundButWrongLine | 2 | Indicates a match for an expected pattern, but the match is on the wrong line. |
| MatchFoundButDiscarded | 3 | Indicates a discarded match for an expected pattern. |
| MatchNoneAndExcluded | 4 | Indicates no match for an excluded pattern. |
| MatchNoneButExpected | 5 | Indicates no match for an expected pattern, but this might follow good matches when multiple matches are expected for the pattern, or it might follow discarded matches for the pattern. |
| MatchFuzzy | 6 | Indicates a fuzzy match that serves as a suggestion for the next intended match for an expected pattern with too few or no good matches. |