Views and passed variable scopes

IMO, that data shouldn't be cached at all, and therefore you shouldn't have the option to keep it - just render the view and immediately discard any variables.

Personally, I've found it handy in the past to have any views loaded within another view (like a main layout) to have access to variables set by other views. Other times, it's annoying. But I think there are definitely use cases both ways. It defaults to trashing the data so most people will use it that way, I'm sure, but the option is available if they decide they need it.

I did too think of the view-within-a-view scenario, but it's the same thing - you can pass those variables to it on the spot.

The current behavior can be handy, of course (otherwise it wouldn't exist), but if it does remain as an optional feature then it has to really be optional all the way. If I don't turn it on, I wouldn't expect any variables to be cached behind the scenes just so they can be later reset by default.