Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redesign the core actor #112

Merged
merged 10 commits into from
May 1, 2020
Merged

Redesign the core actor #112

merged 10 commits into from
May 1, 2020

Conversation

Neverlord
Copy link
Member

To keep #89 focused on functional changes, this is the 'first chunk' of the mixin redesign. This prepares the core actor for the next transformations by:

  • Bundling streaming logic in new alm::stream_transport class (formerly detail::core_policy)
  • Inheriting from caf::stream_manager directly
  • Removing the obsolete stream_distribution_tree
  • Using inheritance for the core_manager and refactoring core_state

This refactoring phase mostly moves code around and renames some types / variables. There are changes to class hierarchies but the new code should be functionally equivalent. When keeping core_policy.cc and core_policy.hh open while reviewing the new stream_transport, it should be straightforward to track how/where code blocks moved. Having a look at https://github.com/actor-framework/actor-framework/blob/0.17.4/libcaf_core/caf/detail/stream_distribution_tree.hpp also might be helpful, because the code from this class essentially got "inlined" into the new stream_transport.

Neverlord and others added 5 commits April 28, 2020 14:52
- Bundle streaming logic in new alm::stream_transport class
- Inherit from `caf::stream_manager` directly
- Remove the obsolete `stream_distribution_tree`
@jsiwek jsiwek merged commit 8b2c9a9 into master May 1, 2020
@Neverlord Neverlord deleted the topic/neverlord/core-actor-redesign branch May 11, 2020 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants