-
Notifications
You must be signed in to change notification settings - Fork 710
Concat arguments when enabling haddock #10783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
734f4f9
to
8e1f76b
Compare
I think the bug was introduced by 80f0a65, which makes the expression modified in this PR to be non-empty if documentation was enabled. I however don't know if I'm introducing some subtle bug by not ignoring the default args anymore but concatenating them with the user supplied args. |
8e1f76b
to
ad84f9e
Compare
ad84f9e
to
3a43753
Compare
@FinleyMcIlwaine, could you have quick look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Seems ok to me, is there a way to add a test? |
Ping, ping! This is an important fix, let's get it (tested and) merged. Maybe the original reproducer could be used as a test? |
I think a test would be possible to add. I however don't have the time at the moment for doing cabal stuff in my free time. |
@FinleyMcIlwaine double-ping! Can we have confirmation that this goes in the direction you intended in your last patch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to see a test, if only for the concatenation logic.
Thanks a lot @jasagredo! :) |
I can add a test for this issue in the next week. |
Sorry for the delay here, this looks good to me! Nice catch |
Thank you both. :) |
Arguments were unioned with <> which is left-biased, therefore -haddock swallowed all other args as indeed described in haskell#10782. I think the bug was introduced by 80f0a65, which makes the expression modified in this PR to be non-empty if documentation was enabled. Fixes haskell#10782
42f263b
to
899899f
Compare
I have pushed onto your branch @jasagredo
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent, thank you very much!
Awesome @mpickering! Thank you very much for taking care of the PR |
@jasagredo: is this ready? Could you set the merge label? @Swordlash: can you confirm this fixes you issue? |
@jasagredo seems busy, so let me set the label, given that users are clamoring for a bugfix release. |
@mergify backport 3.14 |
✅ Backports have been created
|
* Concat arguments when enabling haddock Arguments were unioned with <> which is left-biased, therefore -haddock swallowed all other args as indeed described in #10782. I think the bug was introduced by 80f0a65, which makes the expression modified in this PR to be non-empty if documentation was enabled. Fixes #10782 * Add test for #10783 (concatenate arguments when enabling haddock) --------- Co-authored-by: Matthew Pickering <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit ef29ebb)
Backport #10783: Concat arguments when enabling haddock
Arguments were unioned with
<>
which is left-biased, therefore-haddock
swallowed all other args as indeed described in #10782.QA
The example in #10782 now correctly will fail even if documentation is enabled.
Template Α: This PR modifies behaviour or interface
Include the following checklist in your PR:
significance: significant
in the changelog file.