Very innovative. But then you will have to keep a record of the ones that have been marked for "extra optimizations" (as you suggest).
Anuj On 6 March 2010 02:47, rogerdpack <[email protected]> wrote: > > >> We actually already do this in Rubinius, but we do it in the JIT > directly. It's far less problematic than generating C code that you have to > figure out how to link back in, plus we can inline methods, all that without > loosing any backtrace information. > > It's good that Rubinius does this already. My thought for further > improvements would be something like allowing the User to give the VM > hints, like > > VM.I_promise_to_not_define_any_more_methods_or_change_class_hierarchies_after_this_point > > Then the JIT VM could be"tighter" in its method cacheing. > > Thoughts? > -rp > > -- > --- !ruby/object:MailingList > name: rubinius-dev > view: http://groups.google.com/group/rubinius-dev?hl=en > post: [email protected] > unsubscribe: [email protected] -- Anuj DUTTA -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected]
