Issue #20044 has been updated by mame (Yusuke Endoh). I noticed that the patch outputs a warning. ``` $ ./local/bin/ruby --parser=prism -e '' ./local/bin/ruby: warning: The compiler based on the Prism parser is currently experimental and compatibility with the compiler based on parse.y is not yet complete. Please report any issues you find on the `ruby/prism` issue tracker. ``` @matz said that it would be better *not* to output the warning. However, he also said that if you (the Prism developers) wanted to print it out, he would not stop the warning. FYI. ---------------------------------------- Bug #20044: Add runtime flag and environment variable for prism https://bugs.ruby-lang.org/issues/20044#change-105719 * Author: HParker (Adam Hess) * Status: Closed * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- To enable prism to be used as the parser when running Ruby code, I would like to add a runtime flag and environment variable that allow it to be enabled. The flags could be, ``` ruby --prism test.rb ``` and the environment variable could be, ``` RUBY_PRISM=1 ruby test.rb ``` Previously implemented here: https://github.com/ruby/ruby/pull/9115, but merged before discussion could happen. Things to be sure to discuss mentioned by @mame,
* What to do with the command-line option when prism becomes the default parser in the future. ** Just remove it, or leave it as a "do nothing" option? * What are the appropriate names. ** In Ruby, not absolutely but the names of features for professional use tend to be long and verbose, while those used by ordinary users tend to be short. * Whether to print a warning when this mode is used.