You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since MemoTrie-0.6.5 which includes a fix for the haddocks has been out since 2016-09-11 I'm wondering why lts-7 and nightly haven't been updated? Is it because of the of the additional dependency on newtype-generics?
Relatedly I'm wondering if working haddocks should be enforced more strictly on stackage as broken haddocks pose quite the inconvenience for all downstream packages.
The text was updated successfully, but these errors were encountered:
Yes the upper bound was introduced in #1863, since MemoTrie added that dependency.
We do enforce haddocks and will put an upper bound in place if haddocks fail unless there are special circumstances (see "expected-haddock-failures" in build-constraints.yaml).
I'm not sure why MemoTrie was added with failing haddocks though, a comment explaining why is missing.
As reported in conal/MemoTrie#10 and commercialhaskell/stack#2719, MemoTrie-0.6.4 has broken haddocks, which makes it hard to generate haddocks for packages that depend on it.
Since MemoTrie-0.6.5 which includes a fix for the haddocks has been out since 2016-09-11 I'm wondering why lts-7 and nightly haven't been updated? Is it because of the of the additional dependency on
newtype-generics
?Relatedly I'm wondering if working haddocks should be enforced more strictly on stackage as broken haddocks pose quite the inconvenience for all downstream packages.
The text was updated successfully, but these errors were encountered: