this makes sense to me. seems more like a nice abstraction.

Although, this should not be confused with the debugging stuff of dust.log which serves a different purpose. Or Maybe not I'm not sure. Can we distinguish between the messages being written by the template developer, the template code, the Dust helper code, the Dust core code or some runtime error.

We may have some back-compat issues to work out if we choose to go this way.