A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://cplusplus.github.io/LWG/issue4191 below:

P1467 changed the return type of pow(complex<float>, int)

This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of WP status.

4191. P1467 changed the return type of pow(complex<float>, int)

Section: 29.4.10 [cmplx.over] Status: WP Submitter: Tim Song Opened: 2025-01-10 Last modified: 2025-02-16

Priority: Not Prioritized

View all other issues in [cmplx.over].

View all issues with WP status.

Discussion:

Before C++20, 29.4.10 [cmplx.over] says that this produces a complex<double>. This was confirmed by LWG 844(i) and consistent with C99.

P1467 changed the return type to complex<common_type_t<float, int>>, which is complex<float>. This is a breaking change that does not appear to have been intentional.

[2025-02-07; Reflector poll]

Set status to Tentatively Ready after eight votes in favour during reflector poll.

[Hagenberg 2025-02-16; Status changed: Voting → WP.]

Proposed resolution:

This wording is relative to N5001.

  1. Modify 29.4.10 [cmplx.over] as indicated:

    -3- Function template pow has additional constexpr overloads sufficient to ensure, for a call with one argument of type complex<T1> and the other argument of type T2 or complex<T2>, both arguments are effectively cast to complex<common_type_t<T1, T3 T2>> , where T3 is double if T2 is an integer type and T2 otherwise. If common_type_t<T1, T3 T2> is not well-formed, then the program is ill-formed.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4