8000 gh-131798: Use `sym_new_type` instead of `sym_new_not_null` for _BUILD_STRING, _BUILD_SET by Zheaoli · Pull Request #132564 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content
Prev Previous commit
Next Next commit
Update code
Signed-off-by: Manjusaka <me@manjusaka.me>
  • Loading branch information
Zheaoli committed Apr 26, 2025
commit 9e743747da8eb74509222395a00f4f7ad07231af
7 changes: 4 additions & 3 deletions Python/optimizer_bytecodes.c
Original file line number Diff line number Diff line change
Expand Up @@ -948,14 +948,15 @@ dummy_func(void) {
list = sym_new_type(ctx, &PyList_Type);
}

op(_BUILD_MAP, (values[oparg*2] -- map)) {
map = sym_new_type(ctx, &PyDict_Type);
}

op(_BUILD_SLICE, (values[oparg] -- slice)) {
slice = sym_new_type(ctx, &PySlice_Type);
}

op(_BUILD_MAP, (values[oparg*2] -- map)) {
map = sym_new_type(ctx, &PyDict_Type);
}

op(_BUILD_STRING, (values[oparg] -- str)) {
str = sym_new_type(ctx, &PyUnicode_Type);
}
Expand Down
Loading
0