diff options
| author | Jean Boussier <byroot@ruby-lang.org> | 2023-10-27 16:41:03 +0200 |
|---|---|---|
| committer | Jean Boussier <jean.boussier@gmail.com> | 2023-10-27 21:09:03 +0200 |
| commit | 4aee6931c35a80af846f7100cb8aa1525618e580 (patch) | |
| tree | 73a6039a530768d14cae595b2ccbd563257f2152 /test/ruby/test_method_cache.rb | |
| parent | d654d580f388a1ffc60e74d4b05f753c884ec543 (diff) | |
Make get_next_shape_internal idempotent
Since the check for MAX_SHAPE_ID was done before even checking
if the transition we're looking for even exists, as soon as the
max shape is reached, get_next_shape_internal would always return
`TOO_COMPLEX` regardless of whether the transition we're looking
for already exist or not.
In addition to entirely de-optimize all newly created objects, it
also made an assertion fail in `vm_setivar`:
```
vm_setivar:rb_shape_get_next_iv_shape(rb_shape_get_shape_by_id(source_shape_id), id) == dest_shape
```
Diffstat (limited to 'test/ruby/test_method_cache.rb')
0 files changed, 0 insertions, 0 deletions
