Reclaim one VALUE
from rb_classext_t
by shrinking super_classdepth
#13319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By making
super_classdepth
uint16_t
, classes and modules can now fit in 160B slots again.The downside of course is that before
super_classdepth
was large enough we never had to care about overflow, as you couldn't realistically create enough classes to ever go over it.With this change, while it is stupid, you could realistically create an ancestor chain containing 65k classes and modules.
@jhawthorn thoughts?
Also cc @tagomoris