Repository navigation
Report the computed prime count, not the requested count - #3
Merged
Merged
Conversation
The Node and Rust agents responded "Found first {count} Mersenne primes"
using the requested count, but the exponent table caps at 26 entries.
Asking for 100 returned "Found first 100 Mersenne primes" while 26 were
computed. Both agents now report the actual number computed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug fixed
Bug 6 — agents claim the requested count. The exponent table has 26 entries, but the response text used the requested count:
Both agents now report
primes.length/primes.len().Stacked on #2 (touches the same response-formatting lines); retarget to
mainafter #2 merges.🤖 Generated with Claude Code