Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
A
Actor Framework
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
cpp-libs
Actor Framework
Commits
4a28ddea
Unverified
Commit
4a28ddea
authored
Jun 06, 2021
by
Raphael Zulliger
Committed by
GitHub
Jun 06, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typo
parent
7604b966
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
manual/Actors.rst
manual/Actors.rst
+1
-1
No files found.
manual/Actors.rst
View file @
4a28ddea
...
@@ -186,7 +186,7 @@ lightweight as event-based actors and thus do not scale up to large numbers.
...
@@ -186,7 +186,7 @@ lightweight as event-based actors and thus do not scale up to large numbers.
The primary use case for blocking actors is to use a ``scoped_actor``
The primary use case for blocking actors is to use a ``scoped_actor``
for ad-hoc communication to selected actors. Unlike scheduled actors, CAF does
for ad-hoc communication to selected actors. Unlike scheduled actors, CAF does
**not** dispatch system messages to special-purpose handlers. A blocking
**not** dispatch system messages to special-purpose handlers. A blocking
actor
s
receives *all* messages regularly through its mailbox. A blocking
actor receives *all* messages regularly through its mailbox. A blocking
actor is considered *done* only after it returned from ``act`` (or
actor is considered *done* only after it returned from ``act`` (or
from the implementation in function-based actors). A ``scoped_actor``
from the implementation in function-based actors). A ``scoped_actor``
sends its exit messages as part of its destruction.
sends its exit messages as part of its destruction.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment