Yukihiro Matsumoto wrote:
> Hi,
> 
> In message "Re: [ruby-core:22336] Floats are freezeable and taintable?"
>     on Mon, 23 Feb 2009 05:22:35 +0900, Charles Oliver Nutter <charles.nutter / sun.com> writes:
> 
> |In adding an optimization for Float I realized that Float objects are 
> |both freezable and taintable. Is there a reason for this? It makes it 
> |impossible to, for example, cache literal float objects, make them 
> |immediate, make them pass-by-value (e.g. on stack), and so on. Is there 
> |a reason floats are freezable and taintable?
> 
> Since they are plain objects, but we do guarantee no identity for any
> two float object, I think there's no obstacle to make it cache them.
> Do you think any additional change we need to make it immediate, for
> example?

Other than making freeze and taint (and untrust on 1.9) behave the same 
as Fixnum, I don't think so. These are the only things I ran into when I 
added immediate caching of Floats to JRuby.

- Charlie