From: "Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>
Date: 2024-09-27T14:45:14+00:00
Subject: [ruby-core:119318] [Ruby master Feature#14844] Future of RubyVM::AST?

Issue #14844 has been updated by Eregon (Benoit Daloze).

Status changed from Assigned to Rejected

These days, I believe there is no value to make `RubyVM::AbstractSyntaxTree` stable.
The official Ruby API to parse Ruby code is the Prism API (regardless of which parser is used internally), as matz said.

----------------------------------------
Feature #14844: Future of RubyVM::AST? 
https://bugs.ruby-lang.org/issues/14844#change-109928

* Author: rmosolgo (Robert Mosolgo)
* Status: Rejected
* Assignee: yui-knk (Kaneko Yuichiro)
----------------------------------------
Hi! Thanks for all your great work on the Ruby language. 

I saw the new RubyVM::AST module in 2.6.0-preview2 and I quickly went to try it out. 

I'd love to have a well-documented, user-friendly way to parse and manipulate Ruby code using the Ruby standard library, so I'm pretty excited to try it out. (I've been trying to learn Ripper recently, too: https://ripper-preview.herokuapp.com/, https://rmosolgo.github.io/ripper_events/ .)

Based on my exploration, I opened a small PR on GitHub with some documentation: https://github.com/ruby/ruby/pull/1888

I'm curious though, are there future plans for this module? For example, we might: 

- Add more details about each node (for example, we could expose the names of identifiers and operators through the node classes)
- Document each node type 

I see there is a lot more information in the C structures that we could expose, and I'm interested to help out if it's valuable. What do you think? 



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/