From: Josh Cheek <josh.cheek@...>
Date: 2012-01-29T14:31:30+09:00
Subject: Re: Why is a = a nil instead of giving NameError

--f46d0444ee736e2d7904b7a409b8
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 27, 2012 at 6:56 PM, Navindra Umanee <navindra@cs.mcgill.ca>wrote:

> Thanks for that.
>
> I was hoping it was for a cool reason or that it enabled some cool
> usage, but seems like it's more of an implementation consequence than
> any intentional effect.
>
> --
> Posted via http://www.ruby-forum.com/.
>
>
It enables

a ||= whatever
a &&= whatever

Which I think is "cool", but at the very least, is incredibly useful (the
former more than the latter).

Anyway, in case anyone hasn't seen it, this comes from
https://www.destroyallsoftware.com/talks/wat

--f46d0444ee736e2d7904b7a409b8--