Does Groovy's MetaClassRegistry cache return stale GPath results after concurrent ExpandoMetaClass modifications?
Meta-Class Cache Consistency Under Concurrent Modifications Investigate whether Groovy's internal method cache can return stale GPath evaluation results when ExpandoMetaClass modifications occur concurrently across multiple threads. The goal is to determine if MetaClassRegistry maintains cache consistency without explicit invalidation during runtime metaclas