Partition truncate with deferred invalidation, any side effects?

Hello community,

I'm planning to make a presentation on truncate in Oracle community, in which I'm going to introduce some of the new features introduced in 12c, specifically "deferred invalidation" option. I would like to share my small findings here.

Traditionally, truncating a partition will invalidate all the associated cursors in library cache, and eventually require hard parses on next execution.

With the deferred invalidation option like the following example, it is now possible not to make that happen anymore. Throughout my quick observation, I found cursors with full table scan or index range scan with local indexes will not be invalidated with truncating a partition.