pack
O(n) Convert a String into a ByteString
For applications with large numbers of string literals, pack can be a bottleneck.
O(n) Convert a String into a Text.
Subject to fusion. Performs replacement on invalid scalar values.
O(n) Convert a String into a Text. Subject to fusion. Performs replacement on invalid scalar values.
O(n) Convert a '[Word8]' into a ByteString.
For applications with large numbers of string literals, pack can be a bottleneck. In such cases, consider using packAddress (GHC only).
This program is meant as a tool for suggesting version change of libraries. It tries to match official Package Versioning Policy.
See http://www.haskell.org/haskellwiki/Package_versioning_policy for details.
This version works by inspecting new/removed exported modules or entities. It doesn't currently check the types of exported elements.
Typical invocation:
> package-vt module-ver-1.hs module-ver-2.hs
If you unpack modules with cabal unpack you can use the following form:
> # unpack modules
> cabal unpack package-1
> cabal unpack package-2
> package-vt module-1/module.cabal module-2/module.cabal
Version 0.1.3.3
O(n). Construct a new ByteString from a CString. The resulting ByteString is an immutable copy of the original CString, and is managed on the Haskell heap. The original CString must be null terminated.
O(n). Construct a new ByteString from a CStringLen. The resulting ByteString is an immutable copy of the original CStringLen. The ByteString is a normal Haskell value and will be managed on the Haskell heap.
This provides a library and command line tool for checking if the upper bounds in your package's dependency list excludes the newest package available. The code was originally available only as a web interface at http://packdeps.haskellers.com/, but is now available for standalone use as well.
The command line tool has an incredibly simple interface: simply pass it a list of cabal files, and it will tell you what dependencies- if any- are restricted.
Version 0.3.0.1
(Deprecated) Packed Strings.
Version 0.1.0.1
An implementation of the first-fit, modified-first-fit, last-fit, best-fit, sum-of-squares-fit, worst-fit, and almost-last-fit bin packing heuristics. Items can be packed in order of both decreasing and increasing size (and, of course, in unmodified order).
The module supports both the standard (textbook) minimization problem (How many bins do I need?) and the more practical fitting problem (I've got n bins; which items can I take?).
The API is simple and the module is documented with Haddock (complete with examples). The implementation of the above-mentioned heuristics is complete and partially tested with QuickCheck. However, note that speed has not been a primary concern to date.
Patches and feedback are very welcome.
Version 0.4
Show more results