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 removes the
raj/message
module.Presenting Raj to a group it seemed that the focus fell onto the syntax of pattern matching and how state changes are defined. Those concerns are not really relevant to Raj as there is no assumption made how you model your state changes, just that there are state changes.
While I prefer
raj/message
style messages and pattern matching, I think it is going to be problematic for people trying to build around Raj ifraj/message
is taken to be the approved way of doing things, especially since the API would have been very minimal forever.The module had only ever been included for convenience and had no strong ties to any other module. Before it becomes too pivotal, we should remove it.
I have created
tagmeme
which takesraj/message
and improves upon my original API and is even more strict about the style I prefer. This means someone can create a library that better suits their use case as well. It is no longer a Raj concern.