[expr.throw#2] incorrectly dropping cv-qualifiers CWG2699

[JustAnotherHumanBeing]

This part of the C++ Standard says: Evaluating a throw-expression with an operand throws an exception; the type of the exception object is determined by removing any top-level cv-qualifiers from the static type of the operand and adjusting the type from “array of T” or function type T to “pointer to T” .
One might think that this passage implies that if we are dealing with the operand of type const char[3] , the const qualifier will be removed from it and then char[3] will be adjusted to type char* .

[sdkrystian]

This will be resolved by #3921

[JustAnotherHumanBeing]

According to #3921, "any top-level cv-qualifiers from the type of the (possibly-converted) operand" will be removed. But if they are prvalues, object pointers and function pointers can't have top-level cv-qualifiers.

[sdkrystian]

Yes, no cv-qualifiers would be removed in such cases as there are none to remove. Is that problematic?

[JustAnotherHumanBeing]

Well, that part of the sentence is ambiguously written because it assumes that a reader knows that such prvalues can't have a top-level const.

[sdkrystian]

The end result would still be the same?

[JustAnotherHumanBeing]

Okay.

[jensmaurer]

CWG2699

[frederick-vs-ja]

This should have been fixed by #6328 (3588b7d).