Date: Wed, 10 Dec 2025 20:46:43 -0300
Maybe
auto override a;
I'm not in favor of this feature but coming up with new uses of keywords is
fun.
Em qua., 10 de dez. de 2025, 20:45, Bo Persson via Std-Proposals <
std-proposals_at_[hidden]> escreveu:
> On 2025-12-10 at 22:18, Filip via Std-Proposals wrote:
> > Perhaps this syntax would be interesting:
> >
> > mutable const a = …
> > final a;
> >
> > Using those existing keywords would have a meaning here that a is const
> > after n writes or after manual final
> >
>
> Except that final is not a keyword, but an "identifier with special
> meaning", only when used in certain contexts.
>
> Specifically final and override was not allowed to start a virtual
> function override. It was put at the end instead, to avoid conflicts.
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
auto override a;
I'm not in favor of this feature but coming up with new uses of keywords is
fun.
Em qua., 10 de dez. de 2025, 20:45, Bo Persson via Std-Proposals <
std-proposals_at_[hidden]> escreveu:
> On 2025-12-10 at 22:18, Filip via Std-Proposals wrote:
> > Perhaps this syntax would be interesting:
> >
> > mutable const a = …
> > final a;
> >
> > Using those existing keywords would have a meaning here that a is const
> > after n writes or after manual final
> >
>
> Except that final is not a keyword, but an "identifier with special
> meaning", only when used in certain contexts.
>
> Specifically final and override was not allowed to start a virtual
> function override. It was put at the end instead, to avoid conflicts.
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
Received on 2025-12-10 23:46:56
