RubyVM usage about rbs HOT 8 OPEN

Okay. Reopening this issue. (I don't think I have bandwidth to do this for a while, but someone else would have!)

from rbs.

FYI, a report about this on the truffleruby tracker: oracle/truffleruby#2691

from rbs.

Good point!

I decided to use RubyVM::AbstractSyntaxTree because it's included MRuby and doesn't require additional dependencies. One option would be to make prototype commands an external library and uses parser gem (or something else if exists.)

from rbs.

because it's included MRuby

You mean CRuby, right? I think MRuby doesn't have RubyVM.

One option would be to make prototype commands an external library and uses parser gem (or something else if exists.)

Right, I think that would make sense.

I think moving and stabilizing AbstractSyntaxTree would also be valuable, it seems a few gems decided to use RubyVM::AbstractSyntaxTree but do not realize this is making the gem not portable across Ruby implementations, and using something experimental and unstable. (Just moving under ExperimentalFeatures would also be an option if not making it stable at the same time)

from rbs.

Oh sorry, I mixed CRuby and MRI...

It's great to me too if AbstractSyntaxTree is stable and portable.

I think showing a better error message and exit gracefully is the first step we can do now.

from rbs.

I don't think printing error messages is the best solution for this. Contributions for improvement are welcome.

from rbs.

Could we leave the issue opened?
The error message is an improvement but the original issue is still there: rbs prototype only works on CRuby.

from rbs.

I posted a comment related to this on the RubyVM::AbstractSyntaxTree on the CRuby tracker: https://bugs.ruby-lang.org/issues/14844#note-25

from rbs.