Store visited paths instead of syntaxes in source-code-analysis

[Copilot]

The source-code-analysis object stored a list of enriched syntax objects for each visited form, causing duplicated data and redundant work for nested syntax.

Changes

• Record structure: Store enriched-syntax (entire source, enriched once) and visited-paths (list of syntax-path) instead of visited-forms
• Backward compatibility: Add computed accessor source-code-analysis-visited-forms that uses syntax-ref on enriched syntax with each path
• Property preservation: Extract expander-added properties (e.g., 'class-body) from visits and merge with analyzer properties before enrichment
• Single enrichment pass: Enrich the complete source once instead of per-visit

Usage

Clients can now iterate paths and inspect forms:

(define analysis (source-analyze code #:analyzers analyzers))
(define stx (source-code-analysis-enriched-syntax analysis))
(define paths (source-code-analysis-visited-paths analysis))

;; Inspect visited forms
(for ([path (in-list paths)])
  (define form (syntax-ref stx path))
  ...)

;; Or use backward-compatible accessor
(for ([form (in-list (source-code-analysis-visited-forms analysis))])
  ...)

Reduces memory usage and eliminates duplicated enrichment/logging for nested syntax.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Store visited paths instead of syntaxes</issue_title>
<issue_description>The source-code-analysis object represents the set of visits as a list of syntax objects, each of which is enriched with context and properties from the fully expanded syntax and any expansion analyzers. This results in a lot of duplicated data, especially duplicated logging, as visits of nested syntax objects redo work done by visits of parent syntax objects.

It would be more efficient for the analysis to enrich only the syntax object representing the entire unexpanded source, and separately store a list of visited syntax paths. This would also be conceptually easier to understand. Clients would iterate through the paths and use syntax-ref on the enriched unexpanded syntax to inspect each visited syntax object.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Store visited paths instead of syntaxes #711

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Resyntax analyzed 1 file in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #177

Details

• 30 of 31 (96.77%) changed or added relevant lines in 1 file are covered.
• 10 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.03%) to 92.881%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
private/analysis.rkt	30	31	96.77%

Files with Coverage Reduction	New Missed Lines	%
private/syntax-property-bundle.rkt	10	87.63%

Totals
Change from base Build #172:	-0.03%
Covered Lines:	14664
Relevant Lines:	15788

---

💛 - Coveralls

[github-actions]

Resyntax analyzed 1 file in this pull request and found no issues.

[github-actions]

Resyntax analyzed 1 file in this pull request and found no issues.