Johan Nordlander
Johan Nordlander
Ahh, memory comes back! But Björn is right, all that's missing is a check that foo doesn't contain a competing definition of bar. So trivial that it can wait... :-)
I agree in principle, but there's a catch: we want `?A` to be a base class of every class `A`, even those not yet defined! That requirement fits very badly...
Yes, that's reasonable. The crux is just if the exception handler itself needs to allocate memory... But with unboxed values and fewer witnesses constructed dynamically, memory consumption should become more...
Yep! And I already know where the error is :)
An actor reference is just serialized as the globkey of that actor, so in that aspect, serialization is safe.
Indeed it is! Although I'm not really done implementing the current hierarchy, adding 128-bit types will be nothing but routine.
Would be dead simple to support! Just note that once we implement cancelling of **after** messages, cancellation won't be deterministic in the case a message is directed to some other...
I think this is an excellent idea, shouldn't be hard to implement. Must not forget the RAISE callis in the builtin library, though. Do we want the C source file...
So far we've imagined that the division operator must be overloaded to support at least the following concrete instances: ``` (float, float) -> float (complex, complex) -> complex (int, int)...
That's a good argument! And IDiv makes much sense, not the least as a kind of dual to Times. My only additional thought is what one would do if Duration...