Lars Kroll

Ok, I haven't been in any your meetings recently, so I don't know what else you've been looking at, but here are my thoughts on the subject. I'd be thinking...

Sure, calling ask with a message as argument on an opaque reference and getting a future back is pretty much equivalent to a concurrent/remote object invocation. I still think message-passing...

What's your definition of lazy and eager futures? Eager: Start every computation as soon as all dependencies are available Lazy: Start any computation once the any result is required Those?

Ah, well...it's a bit so and so. So Rust futures themselves are lazy, i.e. nothing happens unless you drive them to completion somehow. But Kompact's ask does eagerly send the...

> I think a good first move might be to try and implement a rough version of one of the use-case algorithms. That is always a good approach in my...

> This change will have to wait until we have some common arcon email. Do we have an actual plan for that that is progressing?^^

Well, domain hunting is not enough. You also need someone to host the mail server, so you can forward the MX records to it. **Edit:** For example, my emails are...

> Seems nice but please do not deprecate the `:=` yet! Please don't deprecate `:=` ever. The `apply` syntax is nice, and I'm happy for people to use it who...

Actually, I would prefer it if that were the expected behaviour, i.e. `render` produces HTML or DOM output, while `toString` tells you what DSL tree you built for debugging purposes....

> Based on those two paragraphs we are doing it wrong: https://github.com/tomas-abrahamsson/gpb/blob/master/src/gpb_compile.erl#L268 Hmm, yeah, so the following change at least gets rid of the not found error for gpb: ```diff...