<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Aug 19, 2017, at 2:02 AM, Susan Cheng &lt;<a href="mailto:susan.doggie@gmail.com" class="">susan.doggie@gmail.com</a>&gt; wrote:<br class=""><div><blockquote type="cite" class="">Hi chris,<br class=""><div class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class=""><br class=""></div><div style="word-wrap:break-word" class="">is a actor guarantee always&nbsp;process the messages in one by one?</div><div style="word-wrap:break-word" class="">so, can it assume that never being multiple threads try to modify the state at the same time?</div></div></div></blockquote><div><br class=""></div><div>Yep, that’s the idea.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div style="word-wrap:break-word" class="">P.S. i have implemented&nbsp;similar idea before:</div><div style="word-wrap:break-word" class=""><br class=""></div><div style="word-wrap:break-word" class=""><a href="https://github.com/SusanDoggie/Doggie/blob/master/Sources/Doggie/Thread/Thread.swift" class="">https://github.com/SusanDoggie/Doggie/blob/master/Sources/Doggie/Thread/Thread.swift</a><br class=""></div><div style="word-wrap:break-word" class=""><a href="https://github.com/SusanDoggie/Doggie/blob/master/Sources/Doggie/SDTriggerNode.swift" class="">https://github.com/SusanDoggie/Doggie/blob/master/Sources/Doggie/SDTriggerNode.swift</a><br class=""></div></div></div></blockquote><br class=""></div><div>Cool. &nbsp;That’s one of the other interesting things about the actor model. &nbsp;We can prototype and build it as a completely library feature to get experience with the runtime model, then move to language support (providing the additional safety) when things seem to work well in practice.</div><div><br class=""></div><div>-Chris</div><div><br class=""></div><br class=""></body></html>