In addition to DevCom-923187, this was previously reported as Microsoft-internal VSO-521345, VSO-153341, VSO-194989, VSO-294538, and VSO-531712.

We resolved those bugs, saying that when LWG-1327 was resolved, the intent was to support floating-point types only. There's a comment in <cmath> about this:

Line 674 in fffbd8f

    
           // The "classification/comparison functions" (fpclassify(), etc.) are exempt, LWG-1327

However, this issue keeps being encountered by users, and I do not see clear language in the current WP justifying our implementation. WG21-N4849 [cmath.syn]/2 simply says "For each set of overloaded functions within <cmath>, with the exception of abs, there shall be additional overloads sufficient to ensure:" and signbit() etc. is a set of overloaded functions within <cmath>.

I believe that either this is a bug in our implementation, or it's a defect in the Standard that needs an LWG issue to be filed (specifically mentioning the "classification/comparison functions" alongside abs).

<cmath>: signbit() misses overloads for integer types #519

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions