diff options
| author | Nobuyoshi Nakada <nobu@ruby-lang.org> | 2024-01-17 16:45:57 +0900 |
|---|---|---|
| committer | Nobuyoshi Nakada <nobu@ruby-lang.org> | 2024-01-22 19:39:34 +0900 |
| commit | 127b19ab561b5365884b465d50356a1e4019713c (patch) | |
| tree | 3efd404748d23a86992531fe287ec34b4f1dd2b9 /mini_builtin.c | |
| parent | 15f6ee057d800d54f803449d6bd4a8aadea524c1 (diff) | |
| download | ruby-127b19ab561b5365884b465d50356a1e4019713c.tar.gz | |
Use line numbers as builtin-index
The order of iseq may differ from the order of tokens, typically
`while`/`until` conditions are put after the body.
These orders can match by using line numbers as builtin-indexes, but
at the same time, it introduces the restriction that multiple `cexpr!`
and `cstmt!` cannot appear in the same line.
Another possible idea is to use `RubyVM::AbstractSyntaxTree` and
`node_id` instead of ripper, with making BASERUBY 3.1 or later.
Diffstat (limited to 'mini_builtin.c')
| -rw-r--r-- | mini_builtin.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/mini_builtin.c b/mini_builtin.c index 457327ee06..8371073f28 100644 --- a/mini_builtin.c +++ b/mini_builtin.c @@ -27,7 +27,6 @@ builtin_iseq_load(const char *feature_name, const struct rb_builtin_function *ta feature_name); } vm->builtin_function_table = table; - vm->builtin_inline_index = 0; static const rb_compile_option_t optimization = { TRUE, /* unsigned int inline_const_cache; */ TRUE, /* unsigned int peephole_optimization; */ |