From: Charles Oliver Nutter <headius@...>
Date: 2010-12-14T18:01:46+09:00
Subject: [ruby-core:33711] Re: Towards a standardized AST for Ruby code

On Tue, Dec 14, 2010 at 2:54 AM, Haase, Konstantin
<Konstantin.Haase@student.hpi.uni-potsdam.de> wrote:
> That would be a great feature and would ease unified behavior amongst different implementations a lot. Also, it would be more stable that trying to parse sourced from files on your own (you could never be sure you actually got the right code, it's not possible for generated code, etc), and would allow other fancy features, like displaying the correct code in the backtrace on the rack error page. Also, I guess this feature is probably not to hard to implement. AFAIK it has been discussed a few times in the Rubinius IRC channel.

We have discussed it as well. It's not especially hard, but it does
eat up memory. Also, for implementations that support ahead-of-time
compilation (like JRuby), you'd ideally not want to ship embedded
source. That could probably be a compiler flag, though.

- Charlie