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

[Ary Borenszweig]

On 9/4/13 11:54 AM, Dicebot wrote:
> On Wednesday, 4 September 2013 at 14:44:50 UTC, Ary Borenszweig wrote:
>> Why would anyone do that?
>
> By an accident - mixins are not hygienic.
>
>> Do you use other people's source code without reading the
>> documentation or reading the source code?
>
> Yes, all the time. Documentation is always lacking and reading full 10
> MLOC code base to tweak a single function is never an option.
>
>> How would the author of "updateGui()" know that you named your
>> variable "st"?
>
> He has no idea how you may name your variables, that is the key point.
> Thus he has no idea what safe symbol names to use.

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?