Lines Matching full:example

32 like "``s`` is a ``string``." Even the first example ("warn ...") shares this form,
64 Example: style-checking names
79 example, the pattern (``functionDecl(...)``) identifies the declaration of the
92 Example: renaming a function
95 Now, let's extend this example to a *transformation*; specifically, the second
96 example above:
104 In this example, the pattern (``declRefExpr(...)``) identifies any *reference* to
106 example. Our edit (``changeTo(...)``) says to *change* the code matched by the
110 Here are some example changes that this rule would make:
122 Example: method to function
165 Example: rewriting method calls
168 In this example, we delete an "intermediary" method call in a string of
169 invocations. This scenario can arise, for example, if you want to collapse a
189 construct a field/method access. In our example, the member access is expressed
240 For example, ``node`` selects the range of source spanned by a particular AST
259     example, the ``access`` function we saw above.
269 example of rewriting method calls.
279 ``RangeSelector`` we saw earlier. For example, we could change the function name
294 multiple edits for each match. For example, suppose we wanted to swap two
298 rather than just a single one. Our example might look like:
337 explicitly exclude the earlier patterns of the list. For example, consider a set
366 minimal code in the definition. For example, given a rule
382 useful, for example, for our method-renaming rule, which is parameterized by the