bug#60691: 29.0.60; Slow tree-sitter font-lock in ruby-ts-mode

[Yuan Fu]

> On Jan 14, 2023, at 12:46 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> 
> On Jan 13 2023, Yuan Fu wrote:
> 
>>> On Jan 13, 2023, at 11:29 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> 
>>>> From: Yuan Fu <casouri@gmail.com>
>>>> Date: Fri, 13 Jan 2023 19:48:40 -0800
>>>> Cc: dgutov@yandex.ru,
>>>> 60691@debbugs.gnu.org,
>>>> juri@linkov.net,
>>>> monnier@iro.umontreal.ca
>>>> 
>>>> Thanks, I pushed a fix for it. I also used intern_c_string in some places 
>>>> like these:
>>>> 
>>>> intern_c_string (":?”)
>>>> intern_c_string (":*")
>>>> 
>>>> I want to change them to use DEFSYM, but what should be the c name for 
>>>> them?
>>> 
>>> Yes, DEFSYM is better in such cases.  The C name can be QCquestion and
>>> QCasterix, for example.
>> 
>> My worry is that they will conflict with, eg, symbol `question’ and 
>> `asterix’, if someone ever defines them in the C codebase. Is that not 
>> possible?
> 
> The C name of the symbol `question' would be Qquestion, without the C
> (which stands for the `:' prefix).

Sorry, I meant `:question’, and `:asterix’. 

Yuan