1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[PRISM] Handle ambiguous_param0 for it and numbered parameters

Browse Source
This commit is contained in:
Kevin Newton 2024-03-13 15:38:44 -04:00
parent 7c9e6eab89
commit 2f8cbd6431
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
prism_compile.c
View File

@ -7008,11 +7008,14 @@ pm_compile_node(rb_iseq_t *iseq, const pm_node_t *node, LINK_ANCHOR *const ret,
break; break;
} }
case PM_NUMBERED_PARAMETERS_NODE: { case PM_NUMBERED_PARAMETERS_NODE: {
body->param.lead_num = ((pm_numbered_parameters_node_t *) scope_node->parameters)->maximum; uint32_t maximum = ((pm_numbered_parameters_node_t *) scope_node->parameters)->maximum;
body->param.lead_num = maximum;
body->param.flags.ambiguous_param0 = maximum == 1;
break; break;
} }
case PM_IT_PARAMETERS_NODE: case PM_IT_PARAMETERS_NODE:
body->param.lead_num = 1; body->param.lead_num = 1;
body->param.flags.ambiguous_param0 = true;
break; break;
default: default:
rb_bug("Unexpected node type for parameters: %s", pm_node_type_to_str(PM_NODE_TYPE(node))); rb_bug("Unexpected node type for parameters: %s", pm_node_type_to_str(PM_NODE_TYPE(node)));