From: Brent Roman <brent@...>
Date: 2009-02-23T06:09:31+09:00
Subject: [ruby-core:22337] Re: Floats are freezeable and taintable?


I'm pretty sure that it is a consequence of Floats not being immediate
objects in MRI.

I think what you are proposing is that the spec disallow any operations on
Floats that
would interfere with implementing them as immediate objects.

If so, this sounds like a good idea to me. 

- brent


Charles Oliver Nutter-2 wrote:
> 
> 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?
> 
> - Charlie
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-ruby-core%3A22336--Floats-are-freezeable-and-taintable--tp22151092p22151582.html
Sent from the ruby-core mailing list archive at Nabble.com.