Fix Pretty
not resetting all global state between calls
#133
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 fixes the long-standing oddity where Goblint prints warnings like
despite using
Pretty.sprint ~width:max_int
, which should avoid such random line breaks.The specific problem was that
Pretty.breakAllMode
was not being reset between differentPretty
calls, so when it became active, following pretty-printing had such odd line breaks.There were two more global variables in
Pretty
which were not being reset:topAlignAbsCol
andaligns
.Now all global variables in
Pretty
are reset and restored properly.