Date: Fri, 20 Feb 2026 11:38:33 -0800
On Fri, Feb 20, 2026 at 11:04 AM Jason McKesson via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> On Fri, Feb 20, 2026 at 1:39 PM Marcin Jaczewski via Std-Proposals
> If it uses an existing `operator->`, then there's no problem.
> `operator->` cannot return a temporary; it must return a pointer. So
Nitpick (possibly just phrasing): `operator->` doesn't have to return
a pointer, it only has to return something that `->` can be applied
to. Which might be a proxy object, and that proxy object's
`operator->` returns a pointer. Once it gets to a raw pointer, then
[expr.ref]{2} takes over.
<std-proposals_at_[hidden]> wrote:
>
> On Fri, Feb 20, 2026 at 1:39 PM Marcin Jaczewski via Std-Proposals
> If it uses an existing `operator->`, then there's no problem.
> `operator->` cannot return a temporary; it must return a pointer. So
Nitpick (possibly just phrasing): `operator->` doesn't have to return
a pointer, it only has to return something that `->` can be applied
to. Which might be a proxy object, and that proxy object's
`operator->` returns a pointer. Once it gets to a raw pointer, then
[expr.ref]{2} takes over.
Received on 2026-02-20 19:38:46
