DR: Reference captures never refer to the capture

[hubert-reinterpretcast]

There is no adjustment to change references to a reference-captured entity to refer to anything else. It is not possible under the wording to reflect upon a reference capture, and when applying reflexpr upon a reference-captured function parameter, the entity being reflected upon is the function parameter. Note that the wording prohibiting reflection via declarations at block scope allows such reflection if the entity is captured (by some random lambda), but does not require reflection upon the capture as opposed to reflection upon the entity.

The ability to reflect upon function parameters of an enclosing function in captureless lambdas should also go away.

If no resolution is forthcoming, let me know, and I'll send a note to CWG.

[camio]

AN: I agree that's a wording defect, I agree that reflecting lambda captures
shouldn't open a loop hole into reflecting entities at block scope.

AN: Hubert, I would appreciate if you could suggest wording that enables
reflection of reference captures to reflect the capture, without allowing
reflection of referenced entities that are forbidden to be reflected.

AN: I would prefer this to be treated as an issue rather than as part of the review process.

HT: Agreed to treat this as an issue. Can we tag this as "cwg" (I can't seem to
edit the labels)?

[camio]

Left open as an issue to handle post-publication.