Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upImprove readability of flow tree dump #8632
Conversation
highfive
commented
Nov 21, 2015
|
Before:
After:
|
ebbbd5e
to
5bbe9ed
|
Why is it |
|
@nox, that's because of the way that the Debug formatter for SpecificFragmentInfo was implemented before. In the latest version of the branch, I've eliminated that behavior. |
|
@bors-servo: r+ |
|
|
|
Might be nice to have a more abbreviated way to represent damage (maybe one letter or Unicode symbol for each flag?) but this is a big improvement as is. |
|
|
Use the PrintTree utility to improve the readability of flow tree dumps. Blocks and fragments are now split over two dump levels, because otherwise they are impenetrable. Also start printing the restyle damage of fragments.
|
|
|
@bors-servo r=pcwalton I fixed the merge conflict by simply resolving some use lines, so I'm resending this to bors. |
|
|
|
|
Improve readability of flow tree dump Use the PrintTree utility to improve the readability of flow tree dumps. Blocks and fragments are now split over two dump levels, because otherwise they are impenetrable. Also start printing the restyle damage of fragments. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8632) <!-- Reviewable:end -->
|
|
|
@bors-servo: retry |
|
|
|
|
mrobinson commentedNov 21, 2015
Use the PrintTree utility to improve the readability of flow tree
dumps. Blocks and fragments are now split over two dump levels, because
otherwise they are impenetrable. Also start printing the restyle damage of
fragments.