Use dynamic dispatch to simplify reporters #10086
Open
+90
−58
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.
Summary
Sort of undecided on this. These are already stored as
dyn Reporter
in each struct, so we're already using dynamic dispatch in that sense. But all the methods takeimpl Reporter
. This is sometimes nice (the callsites are simpler?), but it also means that in practice, you often can't passNone
to these methods that acceptOption<impl Reporter>
, because Rust can't infer the generic type.Anyway, this adds more consistency and simplifies the setup by using
Arc<dyn Reporter>
everywhere.