test: improve coverage for float/float.mbt

[rami3l]

Disclaimer: This PR was generated by an LLM agent as part of an experiment.

Summary

coverage of `float/float.mbt`: 72.7% -> 100%

[peter-jerry-ye-code-review]

‼️ This code review is generated by a bot. Please verify the content before trusting it.

⚠️ [Potential incorrect string representation check for Float::default()]

• Category: Correctness
• Code Snippet: inspect!(Float::default(), content="0")
• Recommendation: Check numeric value directly instead of string representation
• Reasoning: Float::default() should return 0.0 (float zero), but checking against string "0" might be ambiguous. The test could pass incorrectly if the implementation returns integer 0 instead of float 0.0. Consider using expect_eq!-style assertion instead.

⚠️ [Fragile NaN byte pattern assertion]

• Category: Correctness
• Code Snippet: inspect!(f4.to_be_bytes(), content="b\"\\x7f\\xc0\\x00\\x00\"")
• Recommendation: Add comment explaining NaN byte pattern expectation or use NaN check
• Reasoning: The test assumes a specific NaN payload (quiet NaN with zero payload). Different implementations might generate different NaN representations. While the standard defines the quiet NaN bit (MSB of mantissa), the payload bits could vary. Consider: 1) Adding explanatory comment 2) Checking first 2 bytes only 3) Separate sign bit check.

💡 [Duplicated test structure for byte conversions]

• Category: Maintainability
• Code Snippet: Multiple let fN = ... followed by inspect!
• Recommendation: Use parameterized test structure
• Reasoning: The to_be_bytes test repeats the same pattern for different values. Consider creating a test helper function or table-driven test to reduce duplication. Example:

test "to_be_bytes" {
  [
    (0.0, "b\"\\x00\\x00\\x00\\x00\""),
    (-1.0, "b\"\\xbf\\x80\\x00\\x00\"")
  ].for_each(fn((value, expected)) {
    inspect!(value.to_be_bytes(), content=expected)
  })
}

[coveralls]

Pull Request Test Coverage Report for Build 5066

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.05%) to 85.291%

---

Totals
Change from base Build 5056:	0.05%
Covered Lines:	5242
Relevant Lines:	6146

---

💛 - Coveralls