From 127b19ab561b5365884b465d50356a1e4019713c Mon Sep 17 00:00:00 2001 From: Nobuyoshi Nakada Date: Wed, 17 Jan 2024 16:45:57 +0900 Subject: 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. --- mini_builtin.c | 1 - 1 file changed, 1 deletion(-) (limited to 'mini_builtin.c') 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; */ -- cgit v1.2.3