homepage: http://github.com/acw/bytestring-progress
changelog-type: ''
hash: 473161069caf0eb047662301b103a6f7bc6a1bb4a08b681d63e157232d2232b4
test-bench-deps: {}
maintainer: Adam Wick <awick@uhsure.com>
synopsis: A library for tracking the consumption of a lazy ByteString
changelog: ''
basic-deps:
  bytestring: ! '>=0.9 && <1.0'
  base: ! '>=4.0 && <5.0'
  time: ! '>=1.1 && <1.6'
  terminal-progress-bar: ! '>=0.0.1 && <0.0.2'
all-versions:
- '1.0.0'
- '1.0.1'
- '1.0.2'
- '1.0.2.1'
- '1.0.3'
- '1.0.4'
- '1.0.5'
author: Adam Wick <awick@uhsure.com>
latest: '1.0.5'
description-type: haddock
description: ! 'In some cases, it is useful to know how fast a ByteString is being

  consumed. Typically, this could be to report some measure of progress

  to a waiting user, but it could also be to perform some form of testing

  on input / consumption code.'
license-name: BSD3

homepage: http://github.com/acw/bytestring-progress
changelog-type: ''
hash: 960b40832b88742b9eaa4a836090d18b62bfa389b4563eca053f68175cb83755
test-bench-deps: {}
maintainer: Adam Wick <awick@uhsure.com>
synopsis: A library for tracking the consumption of a lazy ByteString
changelog: ''
basic-deps:
  bytestring: ! '>=0.9 && <1.0'
  base: ! '>=4.0 && <5.0'
  time: ! '>=1.1 && <1.8'
  terminal-progress-bar: ! '>=0.0.1 && <0.0.2'
all-versions:
- '1.0.0'
- '1.0.1'
- '1.0.2'
- '1.0.2.1'
- '1.0.3'
- '1.0.4'
- '1.0.5'
- '1.0.6'
author: Adam Wick <awick@uhsure.com>
latest: '1.0.6'
description-type: haddock
description: ! 'In some cases, it is useful to know how fast a ByteString is being

  consumed. Typically, this could be to report some measure of progress

  to a waiting user, but it could also be to perform some form of testing

  on input / consumption code.'
license-name: BSD3

Update from Hackage at 2016-06-06T18:42:31+0000
Update from Hackage at 2016-06-06T18:42:31+0000
