Temporary Table as official materialization method

[timhiebenthal]

Wouldn't this make sense?
Sometimes you don't want to keep intermediate steps in your database schema, but on the other hand with large tables it's more efficient to materialize it once and read it a few times afterwards.
That's were the beauty of temporary tables come in, right?

So the best of both worlds between ephemeral-models and table-models
I know that I could build a real table and have a post-hook to drop it... but why so complicated?

Thoughts?