Switch Ruby's default parser from parse.y to Prism

5 points by tomstuart 9 months ago | 3 comments
  • ksec 9 months ago
    From Matz

    >Prism needs quality and for that it needs to be experimented with on a wider scale. For that reason, I agree with making Prism the default in previews (when Prism passes all tests). Whether it will eventually become the default in 3.4 depends on quality.

    Once it land on master. It will automatically be tested on Github and 37Signals, in addition to Shopify. I remember there were one or two other companies that run on Ruby / Rails master as well. Cookpad? or was it Discourse.

    If we could get Gitlab and Stripe to test against it, and perhaps a few other Ruby shops that doesn't use Rails as representatives then I think Prism is damn well tested.

    Wondering what else is baking in Ruby 3.4. YJIT team has been very quiet....

    • Lio 9 months ago
      > Wondering what else is baking in Ruby 3.4. YJIT team has been very quiet....

      I'm just guessing here but my bet would be inline RBS type information passed to YJIT for provisioning arrays upfront.

      That's a wild guess but based on something that Maxime Chevalier-Boisvert said in her Ruby Kaigi talk Breaking the Ruby Performance Barrier[1].

      If they did that I think it would be amazing for Ruby.

      1. https://www.youtube.com/watch?v=qf5V02QNMnA

      • tomstuart 9 months ago
        Rails’ nightly CI already needed a fix: https://github.com/rails/rails/pull/52937