Catherine

We already use cooperative multitasking on the core device. That was one of the major points of migration to Rust. > Then again, requiring 2 x max_message_size in RAM isn't...

There should be debug information in IR and LLVM should extract line numbers from that. If it doesn't I think there's some option that does it, we might need to...

> My hunch is that the optimization rules won't unroll a loop that iterates over an array due to corner cases That's not how kernel invariants work. Specifically, the field...

> Instead of adding another type (and moving further from Python), how about allowing iteration on tuples whose elements are all the same type? We were planning to always unroll...

> I would do it the other way, in order to stay closer to Python semantics. Support optimized iteration on homogeneous tuples without unrolling, introduce a HeterogeneousCollection (or similarly named)...

Try something like `TFunction({"a": TInt32}, {}, TNone)`.

Ah yes. I don't think you can currently write that annotation. In fact I don't think it's realistic to expect to be able to write annotations for arguments that involve...

Yes. The root cause is I removed the unconditionally_dereferenceable LLVM patch because it was unsound while upgrading to LLVM 6.0. I am reimplementing that in the ARTIQ compiler now.

Yes. I tried to fix this purely in the ARTIQ compiler, and it didn't work. Specifically, hoisting invariant loads requires inlining, which requires devirtualization, which is quite hard to implement...

> What semantics changes are you thinking about? For example, right now all calls are virtual, for several reasons but one of them is that the following code is valid...