Build #1 for multiset-0.3.0
| Package | multiset-0.3.0 |
|---|
| Install | InstallOk |
|---|---|
| Docs | Ok |
| Tests | NotTried |
| Time submitted | 2015-06-29 21:55:42.23221 UTC |
|---|---|
| Compiler | ghc-7.8.3 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | containers-0.5.5.1, base-4.7.0.1 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies...
Downloading multiset-0.3.0...
Configuring multiset-0.3.0...
Building multiset-0.3.0...
Preprocessing library multiset-0.3.0...
[1 of 2] Compiling Data.MultiSet ( Data/MultiSet.hs, dist/build/Data/MultiSet.o )
Data/MultiSet.hs:471:1: Warning:
Local definition of ‘join’ clashes with a future Prelude name - this will become an error in GHC 7.10, under the Applicative-Monad Proposal.
[2 of 2] Compiling Data.IntMultiSet ( Data/IntMultiSet.hs, dist/build/Data/IntMultiSet.o )
Data/IntMultiSet.hs:477:1: Warning:
Local definition of ‘join’ clashes with a future Prelude name - this will become an error in GHC 7.10, under the Applicative-Monad Proposal.
In-place registering multiset-0.3.0...
Running Haddock for multiset-0.3.0...
Running hscolour for multiset-0.3.0...
Preprocessing library multiset-0.3.0...
Preprocessing library multiset-0.3.0...
Data/MultiSet.hs:471:1: Warning:
Local definition of ‘join’ clashes with a future Prelude name - this will become an error in GHC 7.10, under the Applicative-Monad Proposal.
Data/IntMultiSet.hs:477:1: Warning:
Local definition of ‘join’ clashes with a future Prelude name - this will become an error in GHC 7.10, under the Applicative-Monad Proposal.
Haddock coverage:
100% ( 85 / 85) in 'Data.MultiSet'
99% ( 84 / 85) in 'Data.IntMultiSet'
Documentation created: dist/doc/html/multiset/index.html,
dist/doc/html/multiset/multiset.txt
Creating package registration file: /tmp/pkgConf-multiset-0.32214.0
Installing library in
/home/builder/hackage-server/build-cache/tmp-install/lib/x86_64-linux-ghc-7.8.3/multiset-0.3.0
Registering multiset-0.3.0...
Installed multiset-0.3.0
Test log
No test log was submitted for this report.