Skip to content

Compare ValueSlider values bit for bit rather than with Equals - #624

Merged
matt-edmondson merged 2 commits into
mainfrom
claude/project-thread-9lzc74
Oct 11, 2026
Merged

matt-edmondson merged 2 commits into
mainfrom
claude/project-thread-9lzc74

Conversation

@matt-edmondson

Copy link
Copy Markdown
Contributor

Requested by Matt · project thread

Before: SonarCloud failed #622 on S1244 (floating-point equality), raised on the two places ValueSlider used double.Equals to decide whether the value changed. #622 merged before this fix landed on it.

After: no behavior change. Those two comparisons go through IsSameValue, which compares the doubles' bits. That is what Equals was doing in effect, and it says so explicitly, so the finding clears.

How: one private helper in ImGui.Widgets/ValueSlider.cs. The ValueSlider UI suite (18 tests) passes locally.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VX31mmLGVNK3y28fjKiFmB


Generated by Claude Code

Sonar's S1244 counts double.Equals as floating-point equality. The
question is whether anything wrote a new value, which bits answer exactly.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VX31mmLGVNK3y28fjKiFmB
@sonarqubecloud

Copy link
Copy Markdown

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