-
Notifications
You must be signed in to change notification settings - Fork 81
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
haskell_cabal_library: Add haddocks #1102
Conversation
ce3fa9d
to
b3745d1
Compare
b3745d1
to
4dd0f21
Compare
Rebased on master. |
@Profpatsch I've fixed the failure. Waiting for the CI to confirm, but it should be good now |
@regnat do you still want to merge this? |
Well that's up to you ;) I just raised the fact that it makes the build of the cabal packages slower. But if nobody's stepping against it then yes, please merge |
Haddock does add a fair amount of time to build times. Is there some way to make this optional? |
I don't think we can't make it like |
mmh, let's start by merging this. Provided we have an idea of the impact. Could you collect numbers about how much slower |
So I benchmarked building
I guess there has been another change on master making the build slower, I'll see whether I get the same results after a rebase |
(ftr the above results have been generated with |
48e84dd
to
0df0584
Compare
I did some new benchmarks after rebasing on top of master, and indeed we now have a slight slowdown on this branch:
So this makes a 7% slowdown on this example, which I think is acceptable (on a side note, I'd like to know why master seems to be much slower than what it was some times ago. Maybe that's because of #1156 ) |
Build and export the haddocks for `haskell_cabal_library`es
0df0584
to
98f6a24
Compare
Build and export the haddocks for
haskell_cabal_library
esThis builds on top of #1097 because the cabal_wrapper part would have to
be rewritten otherwise (though it's minor and easy to port to master if
#1097 gets delayed)