I've been seeing this for a while now: ``` ../../../../ext/prism/../../src/memchr.c: In function ‘pm_memchr’: ../../../../ext/prism/../../src/memchr.c:35:16: warning: return discards ‘const’ qualifier from pointer target type [-Wdiscarde...Earlopain (Earlopain _)
The current version is too dynamic for rdoc and so C methods like `Ruby::Prism.lex` are not doccumented. Also tweak `Ruby::Prism` introduction. Ruby makes breaking changes in minor versions all the time, no need to call it out.Earlopain (Earlopain _)
Because of the `^^^` hints, it's not valid ruby and so rdoc gives it no syntax highlighting. We can convince it otherwise and syntax-highlight syntax-invalid code. Although it is syntax-invalid, the results look very good. https://gith...Earlopain (Earlopain _)
Same as `current_string`, set it to be empty. Similarly, when populating user-provided options, we need to check the lengh, same as for `encoding`. Closes https://github.com/ruby/prism/issues/4249 https://github.com/ruby/prism/commit/c...Earlopain (Earlopain _)
Currently it loudly returns the correct node and I would simply always ignore this warning because it is just noise. Should I ever hit the case where it is actually different I would never know. On `Ruby::Prism`, I believe that approa...Earlopain (Earlopain _)
Applied in changeset commit:git|f19c5dcd3f68d288112b1b139b6fc75200fba742. ---------- [Bug #22253] Fix UB in prism eval with numbered params locals are just zero-allocated. This leaves their source NULL, which may later be `memcpy`d We...Earlopain (Earlopain _)
locals are just zero-allocated. This leaves their source NULL, which may later be `memcpy`d We don't have to care about numbered params because of https://github.com/ruby/prism/commit/a218a0f265a71aecefe43a1b646917ca37f25547 We don't h...Earlopain (Earlopain _)
Earlopain (Earlopain _)05:08 AM Ruby Revision 479bab3e (git): [ruby/prism] Remove a warning from `discarded-qualifiers`