Internal and external iteration, fibers

[Jacob Carlborg]

On 2013-01-23 22:50, Andrei Alexandrescu wrote:

> It's a subset. That's a better thing than _another_ language.

Of course. But then the CTFE and regular code is handled differently by 
the compiler it will start to become a different language, although very 
similar. I'm wondering if that is even worse.

> Not an argument.

The argument is that it's not code to have two different parts of the 
compiler handling this.

>> In Scala it _is_ the regular compiler that handles both the CTFE and the
>> regular code. A bug in the regular compiler will show up during CTFE as
>> well.
>
> Agreed this is a good thing for Scala, it takes advantage of the jit
> infrastructure.

Exactly, that's what I'm trying to say.


> By passing fresh names as arguments into the function creating it. We
> don't have a strong story there.

The function cannot then generate a symbol that is only used internally 
as a helper without breaking the hygienicy (or what it's called). You 
don't want the user to pass in names for symbols it doesn't know about, 
doesn't care about and should not know about.

-- 
/Jacob Carlborg