Seems like this test got flagged as 'slow' by Google's internal
infrastructure - and that makes me wonder about whether it's appropriate to
have in the lit test suite - we really want to keep these tests as fast as
possible.
I think we're generally OK committing iterator invalidation fixes without
Author: majnemer
Date: Thu Aug 13 18:50:15 2015
New Revision: 244989
URL: http://llvm.org/viewvc/llvm-project?rev=244989&view=rev
Log:
Avoid iteration invalidation issues around MaterializedTemporaryExpr
We risk iterator invalidation issues if we use a DenseMap to hold the
backing storage for an