> For the complete documentation index, see [llms.txt](https://gofast.disasm.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gofast.disasm.dev/built-in-visitors.md).

# Built In Visitors

The **go-fAST** ecosystem includes powerful built-in visitors designed for common patterns of AST analysis and transformation. These visitors encapsulate traversal logic and are ideal for optimization, resolution, and safe rewriting of JavaScript code.

These visitors conform to the `ast.Visitor` interface and can be embedded, extended, or used directly.&#x20;

***

### 🔄 Resolver Visitor

The `resolver` module walks the AST and performs **scope resolution** for:

* **Variable declarations and bindings**
* **Lexical scopes (functions, blocks)**
* **Identifier resolution and context tagging**

#### Use Case

Before performing operations that depend on lexical scoping (e.g. renaming, removing unused vars, or simplifying, you should run:

```go
resolver.Resolve(program)
```

#### What It Adds

* Each identifier is annotated with a **ScopeContext**, which is later used by tools like the `simplifier`
* Can be used to implement tools like dead code elimination or variable mangling

***

### 🧠 Simplifier Visitor

The `simplifier` module walks the AST and performs **semantic simplifications**:

* Constant folding (`1 + 2 -> 3`)
* Logical simplifications (`true && x -> x`)
* Literal optimizations (`'abc'.length -> 3`, `'abc'[0] -> 'a'`)
* Elimination of unnecessary sequence expressions

#### Example

```
data, _ := os.ReadFile("input.js")
ast, _ := parser.ParseFile(string(data))
simplifier.Simplify(ast, true) // also resolves scope
fmt.Println(generator.Generate(ast))
```

#### Benefits

* Safe reduction of redundant logic
* Prunes unnecessary expressions
* Handles tricky edge cases like `typeof`, `instanceof`, `NaN`, `undefined`, etc.
* Maintains runtime side-effects and correctness


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gofast.disasm.dev/built-in-visitors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
