boostorg / boostorg/multiprecision
std::is_integral_v vs std::numeric_limits::is_integer
- Dominant language
- C++
- Stars
- 265
- Forks
- 128
- Avg merge
- 4h 48m
- Merged PRs (30d)
- 2
Description
`std::is_integral_v` returns `0` while `std::numeric_limits::is_integer` returns `1`.
(`using myuint256 = boost::multiprecision::number boost::multiprecision::checked, boost::multiprecision::unchecked), void>>;`)
It is usually assumed that both calls are equivalent.
Is this desired behavior or can it be considered a bug or missing feature?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides no repository files, tests, or entry points. Reproduce the supplied type and compare the two trait results, then inspect the relevant Multiprecision trait and numeric-limits behavior; done requires determining whether the difference is intentional or defining a concrete correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100