FloatingPointConverter fails on narrowing mantissa with explicitJBit
- Dominant language
- Dart
- Stars
- 115
- Forks
- 39
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 1
Description
### Describe the bug
Tests left a hole on changing the mantissaWidth when the output is explicitJBit.
### To Reproduce
Run explicitToExplicit exhaustive with narrowing mantissa and a case will fail.
Need better exhaustive tests, including different exponent and mantissa widths, but also with explicitJBit and now DAZ/FTZ to be tested.
### Expected behavior
_No response_
### Actual behavior
_No response_
### Additional: Dart SDK info
_No response_
### Additional: pubspec.yaml
```yaml
```
### Additional: Context
_No response_
Contributor guide
Research direction
Start with the explicitToExplicit exhaustive test mentioned in the issue and trace it to the FloatingPointConverter implementation. Reproduce the failure with a narrowing mantissa and explicitJBit, then broaden coverage across exponent and mantissa widths, explicitJBit, and DAZ/FTZ cases until the exhaustive tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100