Skip to content

Conversation

@Matthew-Whitlock
Copy link
Collaborator

Depends on PR 95.

I'll have another PR soon for refactoring the namespace from Fenix::->fenix:: so we're more conventional. It's a bunch of find-and-replace for the global fenix_t fenix object, so it would make it annoying to review this PR.

Copy link
Collaborator

@saibalde saibalde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

} else {
error_code = FENIX_ERROR_UNINITIALIZED;
for(auto it = fenix.callbacks.rbegin(); it != fenix.callbacks.rend(); it++){
(*it)(*fenix.user_world, error);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarifying question: new_world and user_world are intended to be effectively the same communicator?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, new_world is just a duplicated user_world for using internally without interfering with the application. It should definitely be renamed for more clarity at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants