Add priority_subject to send priority messages
#84
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello! Thank you for this, but we do not accept unplanned changes to the core libraries. If you have a proposal for a change please open an issue detailing the use cases and the suggested design, along with any other options and considerations. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR attempts to implement priority messaging from OTP 28.0 in a backwards compatible way.
A new
PrioritySubjectis used internally that holds the priority alias, created withpriority_subject(). Its api is identical to a regular subject created withnew_subject, with only its behaviour being different (priority messages enters the queue in front of regular messages). Unfortunatelysend_afterdoes not actually support sending to process aliases, so that remains unimplemented.