Skip to content

If no caller enqueuer is provided to the concrete async message, take the self enquer #2

Description

@AndreaV-Lsi

The Caller Enqueuer provided to the concrete async message is used to notify its completion to the caller and since the mechanism of the notification requires that the caller be an Actor then it makes sense to change the default behavior, to simplify the API, by assuming that if no enqueuer is provided then it is the actor itself that sent the Async Message. This implementation requires a check that the Completion Notification Message has been assigned we could do this by comparing the actual completion notification message to the one read by pulling it out from the default constant of the abstract async message.

Activity

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions