3 ms·
I think the problem is that runPar is currently allowed to return an IVar to the code that called it, which could then pass that IVar into a different runPar in
by elihu 8y ago
I think the problem is that runPar is currently allowed to return an IVar to the code that called it, which could then pass that IVar into a different runPar invocation. That's not something the runtime system expects, or the type system should allow.