added rust syntax example of methods, attributes, functions, impls, structs, enums, unions, tests by pramatias · Pull Request #925 · ast-grep/ast-grep.github.io

pramatias · 2026-02-13T07:44:45Z

Summary by CodeRabbit

Release Notes

Documentation
- Added comprehensive Rust syntax rules for locating and extracting syntactic elements including methods, structs, attributes, traits, functions, enums, and unions.

…tructs, enums, unions, tests

coderabbitai · 2026-02-13T07:45:01Z

📝 Walkthrough

Walkthrough

A new documentation file has been added containing comprehensive ast-grep rules for identifying and extracting Rust syntactic elements. The document provides YAML rule definitions with examples for impl blocks, structs, traits, functions, enums, and other Rust constructs, including capture points for analysis.

Changes

Cohort / File(s)	Summary
Rust AST-grep Rules Documentation `website/catalog/rust/find-top-syntactic-elements.md`	New reference document with 12+ categorized ast-grep rules for locating top-level Rust syntax elements (methods, structs, traits, functions, enums, etc.), including YAML patterns, capture definitions, and illustrative code examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A catalog of rules, so neat and divine,
Where Rust syntax elements in patterns align,
With captures and examples, all perfectly planned,
To find every function and impl in the land! 🌿

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding documentation with Rust syntax examples for various syntactic elements (methods, attributes, functions, impls, structs, enums, unions, tests).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into `main`

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 5

🤖 Fix all issues with AI agents

In `@website/catalog/rust/find-top-syntactic-elements.md`:
- Around line 232-235: The example for trait SomeTrait uses the undeclared
generic T in fn trait_function and must declare it; update the trait definition
to declare the generic parameter (e.g., change trait SomeTrait to trait
SomeTrait<T>) so that fn trait_function(t: T) -> Self is valid, and ensure the
example remains syntactically complete (retain Wrapper usage or document what
Wrapper is if needed).
- Around line 140-144: The trait example uses invalid Rust syntax: the method is
declared with an empty body followed by a trailing semicolon in
SomeTrait::my_function; change the snippet so the method is a proper declaration
(fn my_function();) or, if you intend a default implementation, remove the
trailing semicolon after the body (fn my_function() { /* ... */ }); update the
code block accordingly so the example compiles and matches the intended form
(referencing SomeTrait and my_function).
- Around line 7-452: Add a Playground link under each rule's Example section to
satisfy the rule-page format; for every rule id shown (e.g.,
find-impl-block-methods, find-struct-declarations, find-attribute-items,
find-trait-declarations, find-trait-method-signatures,
find-trait-method-definitions, find-type-aliases, find-enum-items,
find-union-items, find-tests-mod, find-free-functions, find-all-impl-blocks)
insert the standard "Playground" markdown link pointing to the working
playground URL for that rule (use the rule id as the playground parameter or
identifier), ensuring the link appears immediately after the example code block
and follows existing docs styling for other pages.
- Around line 453-662: The "All rules in one file" YAML (id:
find-all-syntactic-elements) is being treated as a rule but lacks required rule
sections; update the document so each rule block includes the mandatory sections
(Title, Playground link, Description, Example code with highlights, Captures,
Pattern or YAML, Diff/Has Fix if applicable, Contributed by) for the YAML rule
shown under "All rules in one file" (the top-level rule with many - all: clauses
such as the impl_item, struct_item, attribute_item, trait_item, function_item,
etc.), or instead move this YAML into an appendix and label it clearly as a
non-rule reference; ensure any captured names (e.g., $METHOD_BODY, $STRUCT_BODY,
$TRAIT_METHOD_BODY, $FUNCTION_BODY, $IMPL_BODY) are documented in a Captures
section if you convert it into a proper rule.
- Around line 75-79: The Rust examples contain invalid syntax: change struct
MyType{} to "struct MyType {}" and terminate tuple/tuple-generic and
const-generic tuple structs Wrapper<T>(T) and Array<T, const N: usize>([T; N])
with semicolons (Wrapper<T>(T); and Array<T, const N: usize>([T; N]);) so they
are valid tuple/array structs, and update the code fence metadata to cover the
three lines (e.g., `{1-3}`) so the corrected examples render properly; refer to
symbols MyType, Wrapper, and Array to locate the snippets.

coderabbitai · 2026-02-13T07:46:56Z

website/catalog/rust/find-top-syntactic-elements.md

+## Impl Block Methods
+
+### Description
+
+Matches `function_item` nodes (methods) that live inside an `impl_item` block, and captures the method name as an `identifier`. Useful for auditing or analyzing the methods of a concrete type implementation.
+
+### YAML
+
+```yaml
+id: find-impl-block-methods
+language: rust
+rule:
+  all:
+    - kind: function_item
+      pattern: $METHOD_BODY
+    - inside:
+        kind: impl_item
+        pattern: $METHOD_IMPL_BODY
+        stopBy: end
+    - has:
+        kind: identifier
+        field: name
+        pattern: $METHOD_NAME
+```
+
+### Captures
+
+- `$METHOD_BODY` — each matched `function_item` node inside the impl
+- `$METHOD_IMPL_BODY` — the matched `impl_item` node (the whole impl block)
+- `$METHOD_NAME` — the `identifier` node for the method's name
+
+### Example
+
+```rs {2}
+impl MyType {
+    fn inherent_method(&self) {}
+}
+```
+
+---
+
+## Struct Declarations
+
+### Description
+
+Matches any `struct_item` node and captures both the full struct declaration and its name. Matches all struct forms: unit structs (`struct Foo;`), tuple structs (`struct Foo(u32);`), and named-field structs (`struct Foo { ... }`).
+
+### YAML
+
+```yaml
+id: find-struct-declarations
+language: rust
+rule:
+  all:
+    - kind: struct_item
+      pattern: $STRUCT_BODY
+    - has:
+        field: name
+        pattern: $STRUCT_NAME
+```
+
+### Captures
+
+- `$STRUCT_BODY` — the entire `struct_item` node (the declaration + body)
+- `$STRUCT_NAME` — the `identifier` node that holds the struct's name
+
+### Example
+
+```rs {1}
+struct MyType{}
+struct Wrapper<T>(T){}
+struct Array<T, const N: usize>([T; N]){}
+```
+
+---
+
+## Attribute Items
+
+### Description
+
+Matches attribute nodes such as `#[derive(...)]`, `#![no_std]`, or any inner/outer attributes. Captures the entire `attribute_item` node.
+
+### YAML
+
+```yaml
+id: find-attribute-items
+language: rust
+rule:
+  all:
+    - kind: attribute_item
+      pattern: $ATTRIBUTES
+```
+
+### Captures
+
+- `$ATTRIBUTES` — the `attribute_item` node(s)
+
+### Example
+
+```rs {1}
+#[derive(Copy, Clone)]
+```
+
+---
+
+## Trait Declaration
+
+### Description
+
+Matches a `trait_item` node and captures the whole trait declaration and its name. Useful for listing all traits in a codebase, or for enforcing naming or documentation conventions at the trait level.
+
+### YAML
+
+```yaml
+id: find-trait-declarations
+language: rust
+rule:
+  all:
+    - kind: trait_item
+      pattern: $TRAIT_BODY
+    - has:
+        field: name
+        kind: type_identifier
+        pattern: $TRAIT_NAME
+```
+
+### Captures
+
+- `$TRAIT_BODY` — the whole trait declaration node
+- `$TRAIT_NAME` — the name of the trait (a `type_identifier`)
+
+### Example
+
+```rs {1}
+trait SomeTrait<T> {
+    fn my_function(){};
+}
+```
+
+---
+
+## Trait Method Signatures (No Body)
+
+### Description
+
+Matches `function_signature_item` nodes inside a trait — method declarations with no body (required methods that implementors must define). Also captures the enclosing trait name so you can correlate each signature with its trait.
+
+### YAML
+
+```yaml
+id: find-trait-method-signatures
+language: rust
+rule:
+  all:
+    - kind: function_signature_item
+      pattern: $TRAIT_METHOD_SIGNATURE
+    - has:
+        field: name
+        kind: identifier
+        pattern: $TRAIT_METHOD_SIGNATURE_NAME
+    - inside:
+        stopBy: end
+        kind: trait_item
+        pattern: $TRAIT_BODY_WITH_METHOD_SIGNATURE
+        has:
+          field: name
+          kind: type_identifier
+          pattern: $TRAIT_NAME_METHOD_SIGNATURE
+```
+
+### Captures
+
+- `$TRAIT_METHOD_SIGNATURE` — the `function_signature_item` node (the signature, no body)
+- `$TRAIT_METHOD_SIGNATURE_NAME` — the `identifier` node for the function name inside the signature
+- `$TRAIT_BODY_WITH_METHOD_SIGNATURE` — the enclosing `trait_item` node
+- `$TRAIT_NAME_METHOD_SIGNATURE` — the trait's `type_identifier`
+
+### Example
+
+```rs {2}
+trait SomeTrait<T> {
+    fn my_function();
+}
+```
+
+---
+
+## Trait Method Definitions (With Body)
+
+### Description
+
+Matches `function_item` nodes inside a trait — method definitions that include a body (provided/default methods). Also captures the enclosing trait name.
+
+### YAML
+
+```yaml
+id: find-trait-method-definitions
+language: rust
+rule:
+  all:
+    - kind: function_item
+      pattern: $TRAIT_METHOD_BODY
+    - has:
+        field: name
+        kind: identifier
+        pattern: $TRAIT_METHOD_NAME
+    - inside:
+        stopBy: end
+        kind: trait_item
+        pattern: $TRAIT_BODY_WITH_METHOD
+        has:
+          field: name
+          kind: type_identifier
+          pattern: $TRAIT_NAME_WITH_METHOD
+```
+
+### Captures
+
+- `$TRAIT_METHOD_BODY` — the `function_item` node (a method definition with a body)
+- `$TRAIT_METHOD_NAME` — the `identifier` node for the function name of the method
+- `$TRAIT_BODY_WITH_METHOD` — the enclosing `trait_item` node
+- `$TRAIT_NAME_WITH_METHOD` — the trait's `type_identifier`
+
+### Example
+
+```rs {2}
+trait SomeTrait {
+    fn trait_function(t: T) -> Self { Wrapper(t) }
+}
+```
+
+---
+
+## Type Alias
+
+### Description
+
+Matches `type_item` nodes (e.g. `type Foo = ...;`) and captures both the full alias declaration and its name.
+
+### YAML
+
+```yaml
+id: find-type-aliases
+language: rust
+rule:
+  all:
+    - kind: type_item
+      pattern: $TYPE_ALIAS_BODY
+    - has:
+        kind: type_identifier
+        field: name
+        pattern: $TYPE_ALIAS_NAME
+```
+
+### Captures
+
+- `$TYPE_ALIAS_BODY` — the whole `type_item` node
+- `$TYPE_ALIAS_NAME` — the `type_identifier` node for the alias name
+
+### Example
+
+```rs {1}
+type Id = u32;
+```
+
+---
+
+## Enum Item
+
+### Description
+
+Matches `enum_item` nodes and captures the entire enum declaration and its name. Works with simple enums, generic enums, and enums with `where` clauses.
+
+### YAML
+
+```yaml
+id: find-enum-items
+language: rust
+rule:
+  all:
+    - kind: enum_item
+      pattern: $ENUM_BODY
+    - has:
+        kind: type_identifier
+        pattern: $ENUM_NAME
+```
+
+### Captures
+
+- `$ENUM_BODY` — the entire enum declaration node
+- `$ENUM_NAME` — the `type_identifier` containing the enum's name
+
+### Example
+
+```rs {1}
+enum Result<T, E>
+where
+    E: std::error::Error,
+{
+    Ok(T),
+    Err(E),
+}
+```
+
+---
+
+## Union Item
+
+### Description
+
+Matches `union_item` nodes and captures the entire union declaration and its name.
+
+### YAML
+
+```yaml
+id: find-union-items
+language: rust
+rule:
+  all:
+    - kind: union_item
+      pattern: $UNION_BODY
+    - has:
+        kind: type_identifier
+        field: name
+        pattern: $UNION_NAME
+```
+
+### Captures
+
+- `$UNION_BODY` — the entire union declaration node
+- `$UNION_NAME` — the `type_identifier` containing the union's name
+
+### Example
+
+```rs {2}
+pub union IntOrFloat {
+    pub i: u32,
+    pub f: f32,
+}
+```
+
+---
+
+## Mod Item Named `tests`
+
+### Description
+
+Matches a `mod_item` whose name is exactly `"tests"` (matched via regex). This is the conventional name for Rust's inline test module, typically annotated with `#[cfg(test)]`.
+
+### YAML
+
+```yaml
+id: find-tests-mod
+language: rust
+rule:
+  all:
+    - kind: mod_item
+      pattern: $TESTS_MOD
+    - has:
+        kind: identifier
+        field: name
+        regex: ^tests$
+```
+
+### Captures
+
+- `$TESTS_MOD` — the entire `mod_item` node
+
+### Example
+
+```rs {2}
+mod tests {
+    #[test]
+    fn test_() {
+        use super::*;
+    }
+}
+```
+
+---
+
+## Free / Top-Level Functions
+
+### Description
+
+Matches any `function_item` node that has an `identifier` for its name. This covers free functions at module scope as well as associated functions (e.g. `fn new() -> Self`). Note that `function_item` also appears inside `impl` and `trait` blocks — use an additional `not: inside:` constraint if you need to exclude those.
+
+### YAML
+
+```yaml
+id: find-free-functions
+language: rust
+rule:
+  all:
+    - kind: function_item
+      pattern: $FUNCTION_BODY
+    - has:
+        kind: identifier
+        field: name
+        pattern: $FUNCTION_NAME
+```
+
+### Captures
+
+- `$FUNCTION_BODY` — the whole `function_item` node
+- `$FUNCTION_NAME` — the `identifier` node for the function's name
+
+### Example
+
+```rs {1}
+fn make_iter() -> impl Iterator<Item = u8> {
+    std::iter::once(1u8)
+}
+```
+
+---
+
+## All Impl Blocks
+
+### Description
+
+Matches every `impl_item` node in the file, regardless of what it implements or whether it has any methods. Useful for a broad scan of all implementations in a codebase.
+
+### YAML
+
+```yaml
+id: find-all-impl-blocks
+language: rust
+rule:
+  all:
+    - kind: impl_item
+      pattern: $IMPL_BODY
+```
+
+### Captures
+
+- `$IMPL_BODY` — the whole `impl_item` node
+
+### Example
+
+```rs {1}
+impl<T> SomeTrait for Wrapper<T> {
+    type Assoc = Wrapper<T>;
+}
+```
+


⚠️ Potential issue | 🟠 Major

Add a Playground link for each rule section.

Each rule is missing the required Playground link, which makes the examples hard to validate and violates the rule-page format. As per coding guidelines, "Provide a working Playground link for each rule."

🤖 Prompt for AI Agents

In `@website/catalog/rust/find-top-syntactic-elements.md` around lines 7 - 452, Add a Playground link under each rule's Example section to satisfy the rule-page format; for every rule id shown (e.g., find-impl-block-methods, find-struct-declarations, find-attribute-items, find-trait-declarations, find-trait-method-signatures, find-trait-method-definitions, find-type-aliases, find-enum-items, find-union-items, find-tests-mod, find-free-functions, find-all-impl-blocks) insert the standard "Playground" markdown link pointing to the working playground URL for that rule (use the rule id as the playground parameter or identifier), ensuring the link appears immediately after the example code block and follows existing docs styling for other pages.

coderabbitai · 2026-02-13T07:46:56Z

website/catalog/rust/find-top-syntactic-elements.md

+```rs {1}
+struct MyType{}
+struct Wrapper<T>(T){}
+struct Array<T, const N: usize>([T; N]){}
+```


⚠️ Potential issue | 🟠 Major

Fix invalid Rust struct examples (tuple/array structs must end with ;).

The tuple and const-generic struct examples are not valid Rust syntax. As per coding guidelines, "Ensure examples are syntactically correct."

✅ Suggested correction

-```rs {1} -struct MyType{} -struct Wrapper<T>(T){} -struct Array<T, const N: usize>([T; N]){} -``` +```rs {1-3} +struct MyType {} +struct Wrapper<T>(T); +struct Array<T, const N: usize>([T; N]); +```

🤖 Prompt for AI Agents

In `@website/catalog/rust/find-top-syntactic-elements.md` around lines 75 - 79, The Rust examples contain invalid syntax: change struct MyType{} to "struct MyType {}" and terminate tuple/tuple-generic and const-generic tuple structs Wrapper<T>(T) and Array<T, const N: usize>([T; N]) with semicolons (Wrapper<T>(T); and Array<T, const N: usize>([T; N]);) so they are valid tuple/array structs, and update the code fence metadata to cover the three lines (e.g., `{1-3}`) so the corrected examples render properly; refer to symbols MyType, Wrapper, and Array to locate the snippets.

coderabbitai · 2026-02-13T07:46:56Z

website/catalog/rust/find-top-syntactic-elements.md

+```rs {1}
+trait SomeTrait<T> {
+    fn my_function(){};
+}
+```


⚠️ Potential issue | 🟠 Major

Trait example uses invalid syntax (method body with trailing ;).

A default method body in a trait should not be followed by ;. As per coding guidelines, "Ensure examples are syntactically correct."

✅ Suggested correction

-```rs {1} -trait SomeTrait<T> { - fn my_function(){}; -} -``` +```rs {1-3} +trait SomeTrait<T> { + fn my_function(); +} +```

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

```rs {1}

trait SomeTrait<T> {

fn my_function(){};

}

```

🤖 Prompt for AI Agents

In `@website/catalog/rust/find-top-syntactic-elements.md` around lines 140 - 144, The trait example uses invalid Rust syntax: the method is declared with an empty body followed by a trailing semicolon in SomeTrait::my_function; change the snippet so the method is a proper declaration (fn my_function();) or, if you intend a default implementation, remove the trailing semicolon after the body (fn my_function() { /* ... */ }); update the code block accordingly so the example compiles and matches the intended form (referencing SomeTrait and my_function).

coderabbitai · 2026-02-13T07:46:56Z

website/catalog/rust/find-top-syntactic-elements.md

+```rs {2}
+trait SomeTrait {
+    fn trait_function(t: T) -> Self { Wrapper(t) }
+}


⚠️ Potential issue | 🟠 Major

Trait method example references undeclared generic T.

T is used without declaring a generic parameter, which is invalid Rust. As per coding guidelines, "Ensure examples are syntactically correct."

✅ Suggested correction

-```rs {2} -trait SomeTrait { - fn trait_function(t: T) -> Self { Wrapper(t) } -} -``` +```rs {2} +trait SomeTrait<T> { + fn trait_function(t: T) -> Self { Wrapper(t) } +} +```

🤖 Prompt for AI Agents

In `@website/catalog/rust/find-top-syntactic-elements.md` around lines 232 - 235, The example for trait SomeTrait uses the undeclared generic T in fn trait_function and must declare it; update the trait definition to declare the generic parameter (e.g., change trait SomeTrait to trait SomeTrait<T>) so that fn trait_function(t: T) -> Self is valid, and ensure the example remains syntactically complete (retain Wrapper usage or document what Wrapper is if needed).

coderabbitai · 2026-02-13T07:46:56Z

website/catalog/rust/find-top-syntactic-elements.md

+### All rules in one file
+
+```yaml
+id: find-all-syntactic-elements
+language: rust
+rule:
+  any:
+    # ------------------------------------------------------------
+    # IMPL BLOCK (contains methods with identifiers)
+    # ------------------------------------------------------------
+    # Matches an `impl_item` that contains one or more `function_item` nodes
+    # (i.e., methods). Each matched function_item must contain an `identifier`
+    # node for the method name.
+    #
+    # Captures:
+    # - $METHOD_BODY     : each matched function_item node inside the impl
+    # - $METHOD_IMPL_BODY: the matched impl_item node (the whole impl block)
+    # - $METHOD_NAME     : the identifier node for the method's name
+    # ------------------------------------------------------------
+    - all:
+        - kind: function_item
+          pattern: $METHOD_BODY
+        - inside:
+            kind: impl_item
+            pattern: $METHOD_IMPL_BODY
+            stopBy: end
+        - has:
+            kind: identifier
+            field: name
+            pattern: $METHOD_NAME
+
+    # ------------------------------------------------------------
+    # STRUCT (with captured name)
+    # ------------------------------------------------------------
+    # Matches a `struct_item` and captures:
+    # - $STRUCT_BODY     : the entire struct_item node (the declaration + body)
+    # - $STRUCT_NAME     : the identifier node that holds the struct's name
+    # ------------------------------------------------------------
+    - all:
+        - kind: struct_item
+          pattern: $STRUCT_BODY
+        - has:
+            field: name
+            pattern: $STRUCT_NAME
+
+    # ------------------------------------------------------------
+    # ATTRIBUTE ITEMS
+    # ------------------------------------------------------------
+    # Matches attribute nodes such as `#[derive(...)]`, `#![no_std]`, or inner
+    # attributes. Captures:
+    # - $ATTRIBUTES      : the attribute_item node(s)
+    # ------------------------------------------------------------
+    - all:
+        - kind: attribute_item
+          pattern: $ATTRIBUTES
+
+    # ------------------------------------------------------------
+    # TRAIT DECLARATION (capture the trait itself)
+    # ------------------------------------------------------------
+    # Matches a `trait_item` and captures:
+    # - $TRAIT_BODY      : the whole trait declaration node
+    # - $TRAIT_NAME      : the name of the trait (a type_identifier)
+    # ------------------------------------------------------------
+    - all:
+        - kind: trait_item
+          pattern: $TRAIT_BODY
+        - has:
+            field: name
+            kind: type_identifier
+            pattern: $TRAIT_NAME
+
+    # ------------------------------------------------------------
+    # METHOD SIGNATURES INSIDE TRAITS (no body)
+    # ------------------------------------------------------------
+    # Matches `function_signature_item` nodes (method signatures inside traits — declaration only).
+    # Captures:
+    # - $TRAIT_METHOD_SIGNATURE            : the function_signature_item node (the signature, no body)
+    # - $TRAIT_METHOD_SIGNATURE_NAME       : the identifier node for the function name inside the signature
+    # - $TRAIT_BODY_WITH_METHOD_SIGNATURE  : the enclosing trait_item node (the trait that contains the signature)
+    # - $TRAIT_NAME_METHOD_SIGNATURE       : the trait's identifier (type_identifier)
+    # ------------------------------------------------------------
+    - all:
+        - kind: function_signature_item
+          pattern: $TRAIT_METHOD_SIGNATURE
+        - has:
+            field: name
+            kind: identifier
+            pattern: $TRAIT_METHOD_SIGNATURE_NAME
+        - inside:
+            stopBy: end
+            kind: trait_item
+            pattern: $TRAIT_BODY_WITH_METHOD_SIGNATURE
+            has:
+              field: name
+              kind: type_identifier
+              pattern: $TRAIT_NAME_METHOD_SIGNATURE
+
+    # ------------------------------------------------------------
+    # METHOD DEFINITIONS INSIDE TRAITS (with body)
+    # ------------------------------------------------------------
+    # Matches `function_item` nodes (method definitions inside traits — include body).
+    # Captures:
+    # - $TRAIT_METHOD_BODY            : the function_item node (a method definition with a body)
+    # - $TRAIT_METHOD_NAME            : the identifier node for the function name of the method
+    # - $TRAIT_BODY_WITH_METHOD       : the enclosing trait_item node (the trait that contains the method)
+    # - $TRAIT_NAME_WITH_METHOD       : the trait's identifier (type_identifier)
+    # ------------------------------------------------------------
+    - all:
+        - kind: function_item
+          pattern: $TRAIT_METHOD_BODY
+        - has:
+            field: name
+            kind: identifier
+            pattern: $TRAIT_METHOD_NAME
+        - inside:
+            stopBy: end
+            kind: trait_item
+            pattern: $TRAIT_BODY_WITH_METHOD
+            has:
+              field: name
+              kind: type_identifier
+              pattern: $TRAIT_NAME_WITH_METHOD
+
+    # ------------------------------------------------------------
+    # TYPE ALIAS (type_item with its identifier)
+    # ------------------------------------------------------------
+    # Matches `type_item` (e.g. `type Foo = ...;`) and captures:
+    # - $TYPE_ALIAS_BODY : the whole type_item node
+    # - $TYPE_ALIAS_NAME : the identifier node (type_identifier) for the alias name
+    # ------------------------------------------------------------
+    - all:
+        - kind: type_item
+          pattern: $TYPE_ALIAS_BODY
+        - has:
+            kind: type_identifier
+            field: name
+            pattern: $TYPE_ALIAS_NAME
+
+    # ------------------------------------------------------------
+    # ENUM ITEM (capture the enum and its name)
+    # ------------------------------------------------------------
+    # Matches an `enum_item` node and captures:
+    # - $ENUM_BODY       : the entire enum declaration node (the whole `enum ... { ... }`)
+    # - $ENUM_NAME       : the identifier node containing the enum's name
+    # ------------------------------------------------------------
+    - all:
+      - kind: enum_item
+        pattern: $ENUM_BODY
+      - has:
+          kind: type_identifier
+          pattern: $ENUM_NAME
+
+    # ------------------------------------------------------------
+    # UNION ITEM (capture the union and its name)
+    # ------------------------------------------------------------
+    # Matches a `union_item` node and captures:
+    # - $UNION_BODY      : the entire union declaration node
+    # - $UNION_NAME      : the identifier node containing the union's name
+    # ------------------------------------------------------------
+    - all:
+      - kind: union_item
+        pattern: $UNION_BODY
+      - has:
+          kind: type_identifier
+          field: name
+          pattern: $UNION_NAME
+
+    # ------------------------------------------------------------
+    # MOD ITEM with identifier "tests"
+    # ------------------------------------------------------------
+    # Matches a `mod_item` where the module name is exactly "tests"
+    # Captures:
+    # - $TESTS_MOD       : the entire mod_item node
+    # ------------------------------------------------------------
+    - all:
+        - kind: mod_item
+          pattern: $TESTS_MOD
+        - has:
+            kind: identifier
+            field: name
+            regex: ^tests$
+
+    # ------------------------------------------------------------
+    # FREE / TOP-LEVEL FUNCTION (function_item)
+    # ------------------------------------------------------------
+    # Matches any `function_item` (free function or associated function)
+    # that has an `identifier` for the function name.
+    #
+    # Captures:
+    # - $FUNCTION_BODY   : the whole function_item node
+    # - $FUNCTION_NAME   : the identifier node for the function's name
+    # ------------------------------------------------------------
+    - all:
+        - kind: function_item
+          pattern: $FUNCTION_BODY
+        - has:
+            kind: identifier
+            field: name
+            pattern: $FUNCTION_NAME
+
+    # ------------------------------------------------------------
+    # ALL IMPL BLOCKS
+    # ------------------------------------------------------------
+    # Matches every `impl_item`. Captures:
+    # - $IMPL_BODY : the whole impl_item node
+    # ------------------------------------------------------------
+    - all:
+        - kind: impl_item
+          pattern: $IMPL_BODY
+```


⚠️ Potential issue | 🟠 Major

“All rules in one file” section is missing required rule sections.

This YAML looks like a rule but lacks the required sections (Playground link, Description, Example code, Captures). Either add the required sections or move this to an appendix clearly marked as non-rule reference. As per coding guidelines, "Include all required sections in each rule: Title (with optional Has Fix badge), Playground link, Description, Pattern OR YAML (delete unused), Example code with highlights, Diff (if has fix), Contributed by."

🤖 Prompt for AI Agents

In `@website/catalog/rust/find-top-syntactic-elements.md` around lines 453 - 662, The "All rules in one file" YAML (id: find-all-syntactic-elements) is being treated as a rule but lacks required rule sections; update the document so each rule block includes the mandatory sections (Title, Playground link, Description, Example code with highlights, Captures, Pattern or YAML, Diff/Has Fix if applicable, Contributed by) for the YAML rule shown under "All rules in one file" (the top-level rule with many - all: clauses such as the impl_item, struct_item, attribute_item, trait_item, function_item, etc.), or instead move this YAML into an appendix and label it clearly as a non-rule reference; ensure any captured names (e.g., $METHOD_BODY, $STRUCT_BODY, $TRAIT_METHOD_BODY, $FUNCTION_BODY, $IMPL_BODY) are documented in a Captures section if you convert it into a proper rule.

added rust syntax example of methods, attributes, functions, impls, s…

64176aa

…tructs, enums, unions, tests

coderabbitai bot reviewed Feb 13, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

added rust syntax example of methods, attributes, functions, impls, structs, enums, unions, tests#925

added rust syntax example of methods, attributes, functions, impls, structs, enums, unions, tests#925
pramatias wants to merge 1 commit intoast-grep:mainfrom
pramatias:add/top-level-syntax-elements

pramatias commented Feb 13, 2026 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Feb 13, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Feb 13, 2026

Uh oh!

coderabbitai bot Feb 13, 2026

Uh oh!

coderabbitai bot Feb 13, 2026

Uh oh!

coderabbitai bot Feb 13, 2026

Uh oh!

coderabbitai bot Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

pramatias commented Feb 13, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Release Notes

Uh oh!

coderabbitai bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

pramatias commented Feb 13, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Feb 13, 2026 •

edited

Loading