Internal and external iteration, fibers

[Daniel Murphy]

"Jacob Carlborg" <doob at me.com> wrote in message 
news:kdlfhr$1676$1 at digitalmars.com...
> Would that be so bad idea, to have a fixed AST representation? The AST 
> presented for the user doesn't need to be the same as the compiler uses 
> internally.
>
> It's the same as any library function. You can easily change the 
> implementation as long as the signature and behavior is the same.
>
> -- 
> /Jacob Carlborg

It depends how much information is in the AST you give the user.  Just 
syntax?  Types?  Full semantic information?

Of course you can transform the internal AST to the user AST, but the more 
information the closer this gets to forcing the compiler to use the user 
AST, or support two ASTs internally.