-
Notifications
You must be signed in to change notification settings - Fork 17
Hoogle/Haddock generation for user project #70
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
Comments
pinging @snoyberg |
(1) seems like a completely safe assumption. I'm uncertain of what (2) means: is it an optimization so that Hoogle databases aren't always generated? My understanding was that Haddock always generated a Hoogle database. |
I've just tested and haddock does not generate Hoogle data by default. You need to specify --hoogle, But it'd simplify things if we could assume Hoogle data should always be generated. I'm assuming that, until corrected. |
That's fine with me. |
BTW, you may want to consider the following proof of concept tool Note: sometimes the latest version of a package can possibly be picked
|
This work item is not approved, but I need a space to document my assumptions (e.g., for work time estimates) and receive feedback.
The text was updated successfully, but these errors were encountered: