Support "default" dispatchers in ExitNodeDispatcher
#3194
Merged
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.
Fixes # .
Summary/Motivation:
This PR significantly simplifies the definition of the
ExitNodeDispatcher
lookup tables by allowing a "default" handler for each node type. In particular, this significantly simplifies the construction of derived dispatchers (like the quadratic dispatcher).Changes proposed in this PR:
ExitNodeDispatcher
ExitNodeDispatcher.__missing__
to cleanly handle fallback from argument-specific handlers to the default handlerLegal Acknowledgement
By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution: