Very WIP Experiment: don't require Box in protocol handler accept #3020
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.
Description
Add an UnboxedProtocolHandler trait and try it out in the examples.
Breaking Changes
The blanket impls for Box and Arc conflict with this, so I had to comment them out
Notes & open questions
Is this worth the effort in simplifying writing protocols?
Should ProtocolHandler always be like this, and we do the transformation to something boxable internally?
Maybe the following would be good:
That way by default people get the simple interface, but if somebody has special requirements such as
they can still do it by implementing BoxedProtocolHandler manually. All ProtocolHandler impls get a default BoxedProtocolHandler impl.
Change checklist