Keean Schupke

> And I thought I was suggesting data types, not OOP subclassing. Sorry my mistake I misinterpreted what you were saying. I think that can work, it would just have...

I think generators and co-routines are the way to go. Everything should be eager unless specifically lazy. That one was easy :-)

Stackless co-routines are cool. Its basically the same as JavaScript's event model. If we are compiling to JavaScript we have to cope with this. If we write an infinite loop,...

What do you think about the actor model?

We could have a first class actor model: ``` actor Queue : list : Nil add : (activity) => list.push(activity) remove : (activity) => // etc ``` The idea is...

Records are data, so would be the messages sent between actors, or in the internal state of actors etc. So actors are not records, actors receive and respond to messages...

Parallelising an algorithm is equivalent to changing the algorithm. Modern super-scalar out-of-order CPUs already exploit the maximum inherant parallelism in code, and they do so at runtime, where there is...

I see what you are talking about. There is no guarantee that the file and the network are not connected. Reading the file may change the result returned from the...

The system does not know the invariants. The file that you read could trigger a network service to change the data downloaded from the network, such that changing the order...

I think there are three scenarios, these must be sequential, these must be parallel, and "don't care". The problem with the above example is it is ambiguous between "must be...