Skip to content

Update kimera to 0.1.4 - #8

Merged
giacope merged 1 commit into
mainfrom
claude/loving-curie-fw2od4
Sep 27, 2026
Merged

giacope merged 1 commit into
mainfrom
claude/loving-curie-fw2od4

Conversation

@giacope

@giacope giacope commented Sep 27, 2026

Copy link
Copy Markdown
Owner

Bumps kimera from 0.1.2 to 0.1.4. The Gemfile now requires >= 0.1.4, and the lockfile changes only the kimera lines. It stays BUNDLED WITH 4.0.16.

0.1.4 no longer mutates guard-style memoization (return @x if @x, return if @_walked then @_walked = true). Those mutants only recompute an equal value, so they always survived.

Full kimera ci run:

survivors
kimera 0.1.2 10
kimera 0.1.4 1

The nine that are gone were in Boundaries, CognitiveScore, Roster, Branches, Ownership and Refs. The one left is >= => > on the fragment prefilter in Duplication::Clusters (line 22). It has nothing to do with memoization and was already there before this bump. It's the prefilter design question left for its own change, so this PR doesn't touch it. The PR gate (--since) doesn't look at that line.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YKVbSpFtuu6QSkB9ZYT1tK


Generated by Claude Code

0.1.4 stops mutating guard-style memoization (`return @x if @x`,
`return if @_walked` then `@_walked = true`), whose mutants only
recompute an equal value. On the full run that clears nine of the ten
survivors 0.1.2 reported, in Boundaries, CognitiveScore, Roster,
Branches, Ownership and Refs.

The tenth, `>= => >` on the fragment prefilter in
Duplication::Clusters, is unrelated to memoization and still survives;
it is the prefilter change left for its own PR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YKVbSpFtuu6QSkB9ZYT1tK
@giacope
giacope merged commit 4c2f7fc into main Sep 27, 2026
4 checks passed
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.

2 participants