Invalidate fastpath when calling attr_writer by super
We started to use fastpath on invokesuper when a method is not refinements since 5c27681813, but we shouldn't have used fastpath for attr_writer either.
cc->aux_.attr_index is for an actual receiver class, while we store its superclass in cc->klass and therefore there's no way to properly invalidate attr_writer's inline cache when it's called by super.
Added by k0kubun (Takashi Kokubun) over 5 years ago
Invalidate fastpath when calling attr_writer by super
We started to use fastpath on invokesuper when a method is not refinements
since 5c27681813, but we shouldn't have used fastpath for attr_writer either.
cc->aux_.attr_indexis for an actual receiver class, while we storeits superclass in
cc->klassand therefore there's no way to properlyinvalidate attr_writer's inline cache when it's called by super.
[Bug #16785]
I suspect the same bug also exists in attr_reader. I'll address that in
another commit.