Created on 2016-03-08.00:00:00 last changed 43 months ago
Notes from the December, 2016 teleconference:
The problem is that overload resolution relies on copy initalization and thus does not describe direct initialization. See also issue 1781.
The term “implicit conversion sequence” is now used in some non-call contexts (e.g., 184.108.40.206 [expr.static.cast] paragraph 4, 7.6.16 [expr.cond] paragraph 4, 7.6.10 [expr.eq] paragraph 4)) and it is not clear that the current definition is suited for these additional uses. In particular, passing an argument in a function call is always copy-initialization, but some of these contexts require consideration of direct-initialization.
|2018-02-27 00:00:00||admin||set||status: open -> drafting|
|2017-02-06 00:00:00||admin||set||messages: + msg5778|