proposal: @mixin functions to auto-mixin at call site

[Dicebot]

On Wednesday, 4 September 2013 at 15:18:10 UTC, Ary Borenszweig 
wrote:
> So the problem is not that implicit mixin is unsafe. The 
> problem is that there's no way to declare a new variable that 
> won't conflict with existing variables in the current scope?

This is the same problem. The key property of mixin is that it is 
unhygienic and invades the caller scope. It is the only entity in 
D that is allowed to do it. Allowing implicit unhygienic 
inclusions is guaranteed to result in accidental symbol clash 
and/or unexpected modification sooner or later.