Issue #20044 has been updated by eightbitraptor (Matthew Valentine-House). Given the precedent set by `mjit` and `yjit` of having short names that mirror the actual project names my preferred approach is having `--prism` but labelling it as `(experimental)` cf. ``` --jit enable JIT for the platform, same as --yjit --mjit enable C compiler-based JIT compiler (experimental) --yjit enable in-process JIT compiler ``` ---------------------------------------- Bug #20044: Add runtime flag and environment variable for prism https://bugs.ruby-lang.org/issues/20044#change-105539 * Author: HParker (Adam Hess) * Status: Open * 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.