From: Charles Oliver Nutter <headius@...>
Date: 2009-06-11T09:46:50+09:00
Subject: Re: ideas for a JIT optimizer

On Wed, Jun 10, 2009 at 6:23 PM, Roger Pack<rogerpack2005@gmail.com> wrote:
> Currently I am thinking that an optimizer that takes
>
> class A
>  def one_thing
>    calls_another 3
>  end
>  def calls_another a
>    a.to_s
>  end
> end
>
> and converts it to C, such that one_thing calls another *in c* would be
> a good  JIT.

It would be *one way* to jit, but it would not allow for polymorphism
(multiple target types providing the same method) or any redefinition.
Nor would it easily allow for methods to be defined at runtime, so
you'd need to make sure both methods exist and choose to statically
bind them (setting that binding in stone) for all time. In this case,
where you're doing a "self" call, as long as there's no subclass and
no method changes at runtime, it's probably ok. But of course you
don't know if it will stay that way forever.

- Charlie