[ruby-core:118060] [Ruby master Bug#20285] Stale inline method caches when refinement modules are reopened

29 May 2024

      Issue #20285 has been updated by k0kubun (Takashi Kokubun).

Backport changed from 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: REQUIRED to 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONE

commit:05787897f69087abdabee926971cdf364bd73730 seems to have backported this to `ruby_3_3`.

----------------------------------------
Bug #20285: Stale inline method caches when refinement modules are reopened
https://bugs.ruby-lang.org/issues/20285#change-108487

* Author: jhawthorn (John Hawthorn)
* Status: Closed
* Assignee: jhawthorn (John Hawthorn)
* Backport: 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONE
----------------------------------------
This is essentially the same issue as #11672, but for inline method caches rather than class caches.

In Ruby 3.3 we started using inline caches for refinements. However, we weren't clearing inline caches when defined on a reopened refinement module.

``` ruby
class C
end

module R
  refine C do
    def m
      :foo
    end
  end
end

using R
def m
  C.new.m
end

raise unless :foo == m()

module R
  refine C do
    alias m m
    def m
      :bar
    end
  end
end

v = m()
raise "expected :bar, got #{v.inspect}" unless :bar == v
```

This will raise in Ruby 3.3 as the inline cache finds a stale refinement, but passes in previous versions.

-- 
https://bugs.ruby-lang.org/