cplusplus / CWG

Core Working Group
23 stars 7 forks source link

[over.match.funcs.general] p7.3 has an error-prone implication #384

Open xmh0511 opened 1 year ago

xmh0511 commented 1 year ago

Full name of submitter (unless configured in github; will be published with the issue): Jim X

[over.match.funcs.general] p7:

Each such case also defines sets of permissible types for explicit and non-explicit conversion functions; each (non-template) conversion function that

  • is a non-hidden member of S,
  • yields a permissible type, and,
  • for the former set, is non-explicit

Note the third bullet, does it mean, for the latter set, the conversion function can be explicit and non-explicit? Why don't we combine the third and second bullets into a single one?

yields a permissible type in the defined set for such kind conversion function