bytestring-progress: A library for tracking the consumption of a lazy ByteString
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.
Flags
Automatic Flags
Name | Description | Default |
---|---|---|
use-system-progressbar | Enable integration with the terminal-progress-bar library. | Enabled |
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
Downloads
- bytestring-progress-1.4.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
Versions [RSS] | 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, 1.0.7, 1.0.8, 1.0.9, 1.2, 1.4 |
---|---|
Dependencies | base (>=4.0 && <5.0), bytestring (>=0.9 && <1.0), terminal-progress-bar (>=0.4 && <0.5), text (>=1.2.3.1 && <1.3), time (>=1.1 && <2.0) [details] |
License | BSD-3-Clause |
Author | Adam Wick <awick@uhsure.com> |
Maintainer | Adam Wick <awick@uhsure.com> |
Category | Control |
Home page | http://github.com/acw/bytestring-progress |
Source repo | head: git clone http://github.com/acw/bytestring-progress |
Uploaded | by AdamWick at 2019-08-28T16:41:49Z |
Distributions | Arch:1.4, Debian:1.4, NixOS:1.4 |
Reverse Dependencies | 1 direct, 0 indirect [details] |
Downloads | 12729 total (30 in the last 30 days) |
Rating | (no votes yet) [estimated by Bayesian average] |
Your Rating | |
Status | Docs available [build log] Last success reported on 2019-08-28 [all 1 reports] |