Avoid unnecessary recompilation due to -haddock #4596
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.
Due to unprincipled adding and removing the
-haddock
flag during compilation and recompilation checking, we were performing more work than necessary.We avoid this by compiling everything with
-haddock
by default. This is safe nowadays, we have essentially been doing this for many releases, and know this is fine.For the occasion where we actually want to parse without the
-haddock
flag, we keep explicitly disabling it.We enable
-haddock
flag during session loading, since we already perform a number of DynFlags tweaks.This behaviour is dependent on the
OptHaddockParse
opton, which can, currently, only be modified at compile-time.Closes #4511