Created on 2019-03-27.00:00:00 last changed 17 months ago
Proposed resolution (approved by CWG 2022-10-21):
Change in 7.7 [expr.const] paragraph 10 as follows:
Anexpression or conversioninvocation is an immediate invocation if it is an explicit or implicit invocation of an immediate function and is not in an immediate function context. An immediate invocation shall be a constant expression.
Additional note, July, 2019:
This issue would appear to be NAD because of the following wording from 7.7 [expr.const] paragraph 10:
An expression or conversion is an immediate invocation if it is an explicit or implicit invocation of an immediate function and is not in an immediate function context. An immediate invocation shall be a constant expression.
[Accepted as a DR at the November, 2022 meeting.]
The intent for immediate functions is that they can only be called at compile time. That rule is enforced by the wording of 7.5.5 [expr.prim.id] paragraph 3:
An id-expression that denotes an immediate function (9.2.6 [dcl.constexpr]) shall appear as a subexpression of an immediate invocation or in an immediate function context (7.7 [expr.const]).
However, this restriction does not apply to implicit function calls such as constructor and operator invocations. Presumably some additional wording is needed for such cases.
History | |||
---|---|---|---|
Date | User | Action | Args |
2023-07-16 13:00:43 | admin | set | status: open -> c++23 |
2023-07-16 13:00:43 | admin | set | status: drwp -> open |
2023-02-18 18:43:04 | admin | set | status: dr -> drwp |
2022-11-25 05:14:04 | admin | set | status: ready -> dr |
2022-10-21 20:41:10 | admin | set | status: review -> ready |
2022-10-21 17:58:11 | admin | set | messages: + msg6951 |
2020-12-15 00:00:00 | admin | set | messages: + msg6221 |
2019-03-27 00:00:00 | admin | create |