It didn't.  `alias_method`, does, though.  The script @xaviershay setup prints out locations of the constructs (like `alias_method`) that do bust the cache.  That surfaced the use of `alias_method` in this file for `parse` and `parse!`.  I didn't see a reason to keep `parse` and `parse!` here -- particularly since they are identical, and usually the bang version is there to indicate that it is somehow _more_ dangerous to use than the non-bang version.