> On 29 Nov 2018, at 01:12, Frank Heckenbach <f.heckenb...@fh-soft.de> wrote: > > Akim Demaille wrote: > >> Wrt to the symbol constructor, you are right to be worried: I don't >> consider it (so far?) to be part of the public API. I do understand >> something like it is needed, but I don't like that it looks safe >> to use. >> >> Would you be ok with parser::unsafe_make_symbol, or something like >> this? > > Sure, though for my taste "unsafe" sounds a bit harsh, perhaps > "unchecked"? If you put in the next release, I'll change my code to > use it.
It seems pretty standard to have lookup tokens with different syntactic behavior, for example when they are declared of different type in a language. So it is worrisome that the typed parser deems the use unsafe.
