One thing stood out to me from the article. They kind of buried this in their tldr. At one point they mentioned using --parser=prism (only in CI) and later state:
While Prism has been merged into CRuby as an library, it has not yet been adopted as the default parser because both the Prism project and the “universal” parser project have been asked to compete.
But it was unclear to whether that flag is for their internal libraries or for the top level ruby interpreter. It looks like this was for ruby, as over in the ruby 3.3 release docs we have both:
Prism is production ready and actively maintained, you can use it in place of Ripper
And
You can now use ruby --parser=prism or ="--parser=prism" to experiment with the Prism compiler. Please note that this flag is for debugging only.
So just pulling 3.3 will give it to you. Though not enabled by default, you can add the flag.
This is huge. The ruby ecosystem needs this.
One thing stood out to me from the article. They kind of buried this in their tldr. At one point they mentioned using
--parser=prism(only in CI) and later state:But it was unclear to whether that flag is for their internal libraries or for the top level ruby interpreter. It looks like this was for ruby, as over in the ruby 3.3 release docs we have both:
And
So just pulling 3.3 will give it to you. Though not enabled by default, you can add the flag.