Kristian Larsson

Right, so I think we need a short term solution because adding exceptions to normal control flow will now print endless amounts of Unhandled Exception messages and that's just not...

In #1586 I have implemented a check so that exceptions are only considered unhandled (and thus printed) in the actor that raised the exception when there is no other actor...

Wohoo, something is working! This might look like ordinary Acton: ```python import base64 actor main(env): i = "foobar" print(i) e = base64.encode(i) print(e) d = base64.decode(e) print(d) if i !=...

I figured I'd pick up on this again. Things have matured in Zig and in my head. One of the primary drivers being able to write functions in Zig is...

Opened #1899 for that switch from C to Zig.

@nordlander this one has got me real stumped. I don't see how this code is any different than most other code we write where we have plenty of actor calls...

This is the smallest reproduction I can find right now: ```python class LogMessage: def __init__(self): pass actor Handler(): def handle(m: LogMessage): pass class Logger: def __init__(self): self.handler = Handler() def...

Calling the actor method in the classes init method works ```python class LogMessage: def __init__(self): pass actor Handler(): def handle(m: LogMessage): pass class Logger: def __init__(self): self.handler = Handler() self.handler.handle(LogMessage())...

Discussed during #1484. This one's a little tricky to solve. Since there is a workaround, it's not top priority. @nordlander should get around to it at a later time.

@nordlander is this a quick fix in codegen or something deeper?