on Wed, 4 Oct 2017 00:16:14 +0200 Benjamin Garrigues <
benjamin.garrig...@gmail.com> wrote:
> Same goes for actors and blocking calls : if you're dealing with a few
coarsed
> grained actors that handle a large state and communicate over an
unreliable
> medium ( such as a network) , you're going to
still need tools to sometimes debug the system. While developing
> a unit testing framework with ability to start actors and easily pass message
> to them can go a long way.
>
> Roope
>
>>
>> Cheers
>> Marc
>>
>> Ursprüngliche Nachricht
>> V
gliche Nachricht
> Von: swift-evolution@swift.org
> Gesendet: 2. Oktober 2017 11:59 vorm.
> An: swift-evolution@swift.org
> Antworten: gerard_igles...@me.com
> Betreff: [swift-evolution] Swift and actors
>
> Hi everybody,
>
> Sadly I don’t have the time to participate on
to follow / debug.
Cheers
Marc
Ursprüngliche Nachricht
Von: swift-evolution@swift.org
Gesendet: 2. Oktober 2017 11:59 vorm.
An: swift-evolution@swift.org
Antworten: gerard_igles...@me.com
Betreff: [swift-evolution] Swift and actors
Hi everybody,
Sadly I don’t have the time to participate
Hi everybody,
Sadly I don’t have the time to participate on all the so interesting discussion
about concurrency and actor stuff.
But I have a question.
I am working for 6 months in the Scala/Akka world, on a project (server stuff
in a docker kubernates world) and after six months of work, and
