You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* href="https://en.wikipedia.org/wiki/Abstract_syntax_tree">AST</a> of {@code expectedPattern}
136
+
* exists in the actual file's AST, in the same order.
137
+
*
138
+
* <p>Methods, constructors, fields, and types that are in the pattern must have the exact same
139
+
* modifiers and annotations as the actual AST. Ordering of AST nodes is also important (i.e. a
140
+
* type with identical members in a different order will fail the assertion). Types must match the
141
+
* entire type declaration: type parameters, {@code extends}/{@code implements} clauses, etc.
142
+
* Methods must also match the throws clause as well.
143
+
*
144
+
* <p>The body of a method or constructor, or field initializer in the actual AST must match the
145
+
* pattern in entirety if the member is present in the pattern.
146
+
*
147
+
* <p>Said in another way (from a graph-theoretic perspective): the pattern AST must be a subgraph
148
+
* of the actual AST. If a method, constructor, or field is in the pattern, that entire subtree,
149
+
* including modifiers and annotations, must be equal to the corresponding subtree in the actual
0 commit comments