Refactor: Replace optimization level with boolean flag
The optimizer now uses a simple boolean flag (`optimization`) instead of an `optimization_level` (u32). This simplifies the optimizer's logic and makes it easier to enable or disable optimizations. The command-line interface and internal testing have been updated to reflect this change.
This commit is contained in:
@@ -53,9 +53,11 @@ Arguments:
|
||||
[FILE] The script file to run or benchmark
|
||||
|
||||
Options:
|
||||
-e, --eval <EVAL> Run a script string directly
|
||||
-b, --bench Run benchmarks (Only allowed in Release mode)
|
||||
-u, --update-bench Update the benchmark baseline (Only allowed in Release mode)
|
||||
-d, --dump Dump the compiled AST
|
||||
-h, --help Print help
|
||||
-V, --version Print version
|
||||
-e, --eval <EVAL> Run a script string directly
|
||||
-b, --bench Run benchmarks (Only allowed in Release mode)
|
||||
-u, --update-bench Update the benchmark baseline (Only allowed in Release mode)
|
||||
-d, --dump Dump the compiled AST
|
||||
-t, --trace Run with TracingObserver enabled
|
||||
--no-opt Disable optimization
|
||||
-h, --help Print help
|
||||
-V, --version Print version
|
||||
|
||||
Reference in New Issue
Block a user