@Earlopain has been prolifically contributing to Prism for over a year, in addition to other various changes around ruby/ruby, like 96fdaf2e, 3826019f, a82e7132, and many more.
I would very much like @Earlopain to be able to merge their own contributions to Ruby, since they have been of such high quality for so long.
This is certainly a bit unexpected to me. I really appreciate your vote of confidence, thank you.
I have spent most of my time for ruby on prism itself:
Mostly the C parser as of late (and rarely prism_compile.c if needed)
Before that, I made sure that the prism AST translation for the parser gem was in a usable state for RuboCop
I do want to make it very clear that I actually have no idea what I'm doing. I never went deep into C as a language and also have no knowledge of parser internals and how they're supposed to work/be written. That seems to have went well enough given this ticket I suppose. Take that as first-hand proof that prism is rather easy to contribute to.
With that disclaimer out of the way, I wouldn't mind it. Prism is a great achievement and I want to make sure that it is as good as it can be, as far as I am able. I like writing Ruby more than writing Ruby tooling in C, but for this I will make an exception (;
+1, @Earlopain has been proactive to fix important prism-related issues reported on this tracker as well as many contributions to making Prism better, and both have proven to be essential.
+1, @Earlopain has helped me on Prism backports to ruby_3_4 and been very helpful. Having them in the team would help us in more places like Prism sync to ruby/ruby.
Updated by 
Updated by 
Updated by 
Updated by