~ Use IntSet instead of ByteString for bitfields.

There are several reasons for this:

* IntSet is stored in ordinary heap, while ByteStrings in pinned memory;
* Our IntSet's should be much faster 90% time. (in typical BT client)
  Hovewer in worst case IntSet is slower, but difference should is not
  so big. (We should measure this although)
* It's pure, tested, error-free and much more convenient.

Moreover we have kill a lot of ugly code!

1 files changed, 2 insertions, 1 deletions

diff --git a/network-bittorrent.cabal b/network-bittorrent.cabal
index 0a89603a..11d371e6 100644
--- a/network-bittorrent.cabal
+++ b/network-bittorrent.cabal
@@ -24,7 +24,6 @@ library
   exposed-modules:     Data.Torrent
                      , Data.Torrent.InfoHash
                      , Data.Bitfield
-                     , Data.Bitfield.Mutable
 
                      , Network.BitTorrent
                      , Network.BitTorrent.Extension
@@ -56,7 +55,9 @@ library
                      , array      >= 0.4
                      , bytestring >= 0.10.2
                      , containers >= 0.4
+                     , intset     >= 0.1
                      , text       >= 0.11.0
+                     , vector
 
                        -- encoding/serialization packages
                      , bencoding  >= 0.1