Allow block argument assignment preference

I’m checking out the latest updates prior to the next release and there are a few things I have to question. This one is the preference for allowing block argument assignment; I think that’s probably a bad thing to have as a default. Surely we should be encouraging fixing of the problematic code?

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Concurrent: an object that looks like a raisin but isn't

+1, arguments should not be assignable.

On Tue, Aug 9, 2016 at 1:59 PM, tim Rowledge <[hidden email]> wrote:
> I’m checking out the latest updates prior to the next release and there are a few things I have to question. This one is the preference for allowing block argument assignment; I think that’s probably a bad thing to have as a default. Surely we should be encouraging fixing of the problematic code?
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Concurrent: an object that looks like a raisin but isn't
>
>
>