Conversation
1ec58f2 to
f843955
Compare
|
Implementation looks good, but there's more to discuss before merging this. I personally tend to use the existing style, though I really don't care either way. Could we perhaps get stats off Hackage for how popular each of the two is (I often see these sorts of stats in GHC proposals etc. - is there an easy way to grab the source of all packages / all popular/maintained packages)? This may need to be put behind a flag. |
|
Yeah, I don't mind getting stats. Is there a tool people use to scrape Hackage? |
I don't know of any off-hand. I'd be interested to know if there is. |
|
Kind reddit user pointed me to https://hackage-search.serokell.io, which seems to work. Unfortunately, as every package uses at least one of |
|
Ended up writing my own script for this: https://github.com/brandonchinn178/hackage-grep Searching for
Note that if any of those packages use |
7091a6c to
df631f2
Compare
c7364ed to
40bcc74
Compare
df631f2 to
dead308
Compare
|
@georgefst FYI this is now behind a flag. Personally, because all official documentation uses |
dead308 to
2bbe8a5
Compare
2bbe8a5 to
a42ddeb
Compare
I'm reluctant to change defaults without good reason. There are arguments on both sides. In particular, the reason I use the current style is consistency with single-line style: |
|
Thanks @georgefst, I won't change the default. Good to merge, then? |
Blocked on #49?
Related to #74
It always kinda bothered me when multiline haddocks were formatted like
The haddock documentation always uses
{-|without the space