[Exploration] Enrich the return value of DSL handlers #2
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.
Through the return value, the handler can:
and should never be repeated again.
The main motivation behind this is to dynamically register
handlers within other handlers (to avoid running out of memory,
this implies the need to unregister handlers).
However, the problem is that dynamically creating a large number
of handlers would not play well with the current appoach of
trying "searching" for the right handler by trying all handlers
for the event type. Indeed, the linear search may be too slow and
wasteful.
There was also a problem with the NoMatch() return value. The
problem is that it is not always trivial to choose between
NoMatch() and OK(). Moreover, sometimes it can lead to potential
vulnerabilities: e.g., if there is an incoming nonsense message
and all message handlers return NoMatch(), the module may return
an error and crash.