From: Matthew Kerwin <matthew@...>
Date: 2013-03-21T04:44:33+09:00
Subject: Re: Why was the object_id for true and nil changed in ruby2.0?

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

Because immediate values have no overhead. It takes memory and cpu cycles
to create an object instance; it takes no (extra) memory if the value is
stored in the reference (ie the object id _is_ the value, albeit slightly
modified), and far fewer cycles to shift and OR some bits.

Sent from my phone, so excuse the typos.

--e0cb4efe2dac48957e04d86073cd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>Because immediate values have no overhead. It takes memory and cpu cycle=
s to create an object instance; it takes no (extra) memory if the value is =
stored in the reference (ie the object id _is_ the value, albeit slightly m=
odified), and far fewer cycles to shift and OR some bits.</p>

<p>Sent from my phone, so excuse the typos.</p>

--e0cb4efe2dac48957e04d86073cd--