Implement Debug for Schedule, Executor and other subtypes #213
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 is an attempt to implement #198. I've followed the guidelines for the
Debug
trait relatively strictly, so it mostly shows the exact internal state of the various types. I could make some of it a bit more clean and easy to read, for example by grouping the values ofExecutor
by index, or showing only the system names instead of the fullSystemId
, but I first wanted some feedback on whether such a deviation from standardDebug
output would be ok.I introduced an instance of
unsafe
in theSystemBox
implementation. I don't know if that is sound, that should be verified by someone who knows better.Perhaps implementing this using the
Debug
trait is the wrong approach here, I just went with that because the original issue described it that way.