Mutation coverage: IMPL-scaleUp

[thedavidmeister]

Adds testScaleUpPowersOfTen: every power of ten in (0, 1e76) and its two neighbours, at exponent 0 and at the least exponent the shift leaves room for (one digit short reverts). A power of ten is the only coefficient that lands exactly on a step threshold, so the < vs <= of each step was only killed when the fuzzer happened to draw one (step 3's survived the pre-existing suite outright).

QA

Discriminating tests: testScaleUpPowersOfTen (alone kills M04, M05, M07-M09, M11-M13, M15-M17, M19-M21, M23-M46; the pre-existing suite left M15 surviving and killed M07/M11/M19/M23/M27 only by fuzz draw)
Mutations applied: 46 via mutation-probe on scaleUp/scaleUpUnguarded: range guard (3), exponent-wrap revert (2), each of 7 steps' threshold raised, lowered, < to <=, multiplier and decrement changed, returned coefficient; M06/M10/M14/M18/M22 (steps 1-5 thresholds lowered one decade) are equivalent, shown exhaustively over all 76 digit counts
Oracle: LibExactFloat.digits on the exact coefficient (shift t = 76 - digits), expected (c * 10^t, e - t) iff e >= int256.min + t, else ScaleUpOutOfRange with the input
Category check: test-only; no src changes

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 49 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: c4a44b75-1e4b-4603-9055-ae5ed75b6ec9

---

📥 Commits

Reviewing files that changed from the base of the PR and between cfa33af and 9f11eec.

---

📒 Files selected for processing (1)

• test/src/lib/implementation/LibDecimalFloatImplementation.scaleUp.t.sol

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[linear]

RAI-3238

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment