No, in that case I would have to use your reification API
(Not yet standard) to express what my_spellable_name
maps to, as you want to restrict our ability to make custom
character mappings - unless I missed something again?

AlisdairM

> On May 28, 2020, at 17:00, Corentin Jabot via SG16 <sg16_at_[hidden]> wrote:
>
>
>
> On Thu, May 28, 2020, 17:51 Hubert Tong via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
> On Thu, May 28, 2020 at 11:32 AM Alisdair Meredith via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
> A more interesting question is whether we expect tools
> to provide a translation layer using \uXXXX in identifiers
> to alias more reasonable names in a user’s native
> encoding?
> +1
>
>
> In that case you could replace by some_prefix_XXXX.
>
> Thinking of running a script to provide a translation of
> a header with more usable names for my working
> environment.
>
> AlisdairM
>
> > On May 28, 2020, at 16:08, Corentin via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
> >
> >
> > Do we really expect people to ever type \uxxxx in C++20.
> > They wouldn't be more or less first class citizen as they are today given we would not changing the requirements on characters must be supported by the physical character set
>
> --
> SG16 mailing list
> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16 <https://lists.isocpp.org/mailman/listinfo.cgi/sg16>
> --
> SG16 mailing list
> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16 <https://lists.isocpp.org/mailman/listinfo.cgi/sg16>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16