ViewString: special case for trees and forests #440
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.
I realised that undirected trees and forests didn't know that they were bipartite, so I've added this implication via an
InstallTrueMethod
.UndirectedSpanningTree
s also didn't know that they were undirected trees, so I've added this too.It then became a bit weird that these digraphs would be shown as
<immutable bipartite symmetric connected digraph...>
or something like that.The
ViewString
s now say "...forest digraph..." and "...tree digraph..." - should I drop the 'digraph'? I thought it best to keep it in, so that it's clear to a user that these are digraph objects, but I'm not strongly of that opinion.