Skip to content

[Backport releases/v4.29.0] feat: add pp.fvars.anonymous option#12744

Merged
kim-em merged 1 commit intoreleases/v4.29.0from
backport-12688-to-releases/v4.29.0
Mar 1, 2026
Merged

[Backport releases/v4.29.0] feat: add pp.fvars.anonymous option#12744
kim-em merged 1 commit intoreleases/v4.29.0from
backport-12688-to-releases/v4.29.0

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 1, 2026

Backport 5dd8d57 from #12688.

This PR adds a `pp.fvars.anonymous` option (default `true`) that
controls the display of loose free variables (fvars not in the local
context).

- When `true` (default), loose fvars display their internal name like
`_fvar.42`
- When `false`, they display as `_fvar._`

This is analogous to `pp.mvars.anonymous` for metavariables. It's useful
for stabilizing output in `#guard_msgs` when messages contain fvar IDs
that vary between runs — for example, in diagnostic tools that report
`isDefEq` failures from trace output where the local context is not
available.

🤖 Prepared with Claude Code

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
(cherry picked from commit 5dd8d57)
@github-actions github-actions bot requested a review from kmill as a code owner March 1, 2026 07:21
@kim-em kim-em merged commit ca43b60 into releases/v4.29.0 Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant