Benoit Vey

It looks like this is an uninitialised type descriptor pointer problem. I'll try digging into it.

I think I got it. This is a premature free issue. Full tracing of `val` objects sent in messages is deferred until a GC cycle on the owner. This means...

I'm not sure. I can see a fix for this but I think it would have some performance penalty. Maybe removing it until we've discussed it on the sync call...

@jkleiser You have to add `use "collections"` at the beginning of the code.

I'm going to implement the `iftype` expression first since the change is straightforward. Function specialisations will require more work and will come later.

There are basically 3 things that need to be done. - At the runtime level, we need to add browser-compatible implementations of the platform-specific parts of the runtime (threading, virtual...

@jemc Possibly, yes. We could also delay the runtime changes by adding blank implementations of the relevant modules. It would result in a single threaded, `malloc`-based runtime with no IO...

This isn't exactly true. The receiver inside of a function is what the receiver capability says it is. So the receiver in a `fun iso` is `iso`. This means that...

I'm going to assign myself to this one.

I've experimented with a few ideas and I think I'm going to split them into two actual RFCs: the first about tidying up the `Seq` interface and resolving some inconsistencies...