A PHP internals mailing list discussion about a proposed RFC for OPcache Static Cache, which would add an OPcache-managed shared-memory cache for userland values and PHP static state. The RFC introduces volatile and persistent backends, new OPcache namespace functions, and two attributes (#[OPcache\VolatileStatic] and #[OPcache\PersistentStatic]) that allow static properties and method static variables to survive across requests. Key discussion points include API design concerns (lock symmetry, atomic decrement behavior, status API returning objects vs arrays), the default-off setting and its impact on library adoption, shared-hosting tenant isolation challenges, multi-library key collision risks, and serialization behavior. The RFC author (Go Kudo) responded with several API improvements including explicit unlock functions, lease-based lock expiry, and granular cache entry deletion.
