How does Ruby optimize method calls using polymorphic inline caches (PIC)?

PIC stores multiple class-method mappings at a call site to speed up dynamic dispatch.

When a method call site sees multiple receiver types, Ruby evolves from monomorphic inline cache (single type fast path) to polymorphic inline cache (multiple cached entries). Each entry maps a receiver class to a resolved method pointer. This avoids full method lookup across inheritance chains.