ruff/crates/ruff_python_ast_integration_tests
Ibraheem Ahmed c9dff5c7d5
[ty] AST garbage collection (#18482)
## Summary

Garbage collect ASTs once we are done checking a given file. Queries
with a cross-file dependency on the AST will reparse the file on demand.
This reduces ty's peak memory usage by ~20-30%.

The primary change of this PR is adding a `node_index` field to every
AST node, that is assigned by the parser. `ParsedModule` can use this to
create a flat index of AST nodes any time the file is parsed (or
reparsed). This allows `AstNodeRef` to simply index into the current
instance of the `ParsedModule`, instead of storing a pointer directly.

The indices are somewhat hackily (using an atomic integer) assigned by
the `parsed_module` query instead of by the parser directly. Assigning
the indices in source-order in the (recursive) parser turns out to be
difficult, and collecting the nodes during semantic indexing is
impossible as `SemanticIndex` does not hold onto a specific
`ParsedModuleRef`, which the pointers in the flat AST are tied to. This
means that we have to do an extra AST traversal to assign and collect
the nodes into a flat index, but the small performance impact (~3% on
cold runs) seems worth it for the memory savings.

Part of https://github.com/astral-sh/ty/issues/214.
2025-06-13 08:40:11 -04:00
..
src Remove cyclic dev dependency with the parser crate (#11261) 2024-05-07 09:24:57 +00:00
tests [ty] AST garbage collection (#18482) 2025-06-13 08:40:11 -04:00
Cargo.toml Move sub-crates to workspace dependencies (#11407) 2024-05-13 14:37:50 +00:00
README.md Remove cyclic dev dependency with the parser crate (#11261) 2024-05-07 09:24:57 +00:00

Integration tests for ruff_python_ast

This crate includes integration tests for the ruff_python_ast crate.

The reason for having a separate crate is to avoid introducing a dev circular dependency between the ruff_python_parser crate and the ruff_python_ast crate.

This crate shouldn't include any code, only tests.

Reference: