Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This package provides a GTK4 bindings generator for Go.
This is a weakref map for Go 1.18, with some inspiration from @urlhttps://github.com/xeus2001/go-weak,xeus2001's weakref implementation.
Orphan instances for TH datatypes. In particular, instances for Ord and Lift, as well as a few missing Show / Eq. These instances used to live in haskell-src-meta, and that's where the version number started.
This is a package somewhat like cdeps which scans .chs files for dependencies.
This package provides functionality for manipulating @FilePath@ values, and is shipped with <https://www.haskell.org/ghc/ GHC>. It provides two variants for filepaths: . 1. legacy filepaths: @type FilePath = String@ . 2. operating system abstracted filepaths (@OsPath@): internally unpinned @ShortByteString@ (platform-dependent encoding) . It is recommended to use @OsPath@ when possible, because it is more correct. . For each variant there are three main modules: . * "System.FilePath.Posix" / "System.OsPath.Posix" manipulates POSIX\/Linux style @FilePath@ values (with @\/@ as the path separator). . * "System.FilePath.Windows" / "System.OsPath.Windows" manipulates Windows style @FilePath@ values (with either @\\@ or @\/@ as the path separator, and deals with drives). . * "System.FilePath" / "System.OsPath" for dealing with current platform-specific filepaths . For more powerful string manipulation of @OsPath@, you can use the <https://hackage.haskell.org/package/os-string os-string package> (@OsPath@ is a type synonym for @OsString@). . An introduction into the new API can be found in this <https://hasufell.github.io/posts/2022-06-29-fixing-haskell-filepaths.html blog post>. Code examples for the new API can be found <https://github.com/hasufell/filepath-examples here>.
This package provides a stable version of Hspec which is used to test the in-development version of Hspec.
Bindings for GdkPixbuf, autogenerated by haskell-gi.
Bindings for Gdk, autogenerated by haskell-gi.
This package provides first class functional references in Van Laarhoven style supporting the following optics: . * Lenses (view, over) . * Traversals (toListOf, matching, over) . * Setters (over) . * Grates (zipWithOf, under, review) . * Resetters (under) . * Adapters (view, review) . * Grids (toListOf, over / under, review) . * Prisms (matching, over / under, review) . * Getters (view) . * Folders (toListOf) . * Reviewers (review).
Various useful functions on tuples, overloaded on tuple size.
Haskell bindings for libarchive. Provides the ability to unpack archives, including the ability to unpack archives lazily.
This package provides a pure interface for compressing and decompressing streams of data represented as lazy ByteStrings. It uses the bz2 C library so it has high performance.
It provides a convenient high level API suitable for most tasks and for the few cases where more control is needed it provides access to the full bzip2 feature set.
This package adds resource management and exception handling to the @pipes@ ecosystem. . Notable features include: . * /Resource Safety/: Guarantee finalization using @finally@, @bracket@ and more . * /Exception Safety/: Even against asynchronous exceptions! . * /Laziness/: Only acquire resources when you need them . * /Promptness/: Finalize resources early when you are done with them . * /Native Exception Handling/: Catch and resume from exceptions inside pipes . * /No Buy-in/: Mix resource-safe pipes with unmanaged pipes using @hoist@.
This package gives you access to the set of operating system services standardised by <http://pubs.opengroup.org/onlinepubs/9699919799/ POSIX.1-2008> (or the IEEE Portable Operating System Interface for Computing Environments - IEEE Std. 1003.1). . The package is not supported under Windows.
This package provides functionality for manipulating @OsString@ values, and is shipped with <https://www.haskell.org/ghc/ GHC>.
Cabal with c2hs dependencies.
@pipes-parse@ builds upon the @pipes@ library to provide shared parsing idioms and utilities: . * /Leftovers/: Save unused input for later consumption . * /Leftover propagation/: Leftovers are propagated backwards perfectly . * /Connect and Resume/: Use @StateT@ to save unused input for later . * /Termination Safety/: Detect and recover from end of input . @Pipes.Parse@ contains the full documentation for this library. . Read @Pipes.Parse.Tutorial@ for an extensive tutorial.
Please see the README on Github at <https://github.com/IvanMalison/gtk-sni-tray#readme>
This package implements an SMTLIB based Horn-Clause\/Logical Implication constraint solver used for Liquid Types. . The package includes: . 1. Types for Expressions, Predicates, Constraints, Solutions 2. Code for solving constraints . Requirements . In addition to the .cabal dependencies you require . * A Z3 (<http://z3.codeplex.com>) or CVC4 (<http://cvc4.cs.nyu.edu>) binary.
@pipes-group@ uses @FreeT@ and lenses to group streams into sub-streams. Notable features include: . * /Perfect Streaming/: Group elements without collecting them into memory . * /Lens Support/: Use lenses to simplify many common operations . @Pipes.Group@ contains the full documentation for this library. . Read @Pipes.Group.Tutorial@ for an extensive tutorial.
Liquid Types for Haskell.
Many recursive functions share the same structure, e.g. pattern-match on the input and, depending on the data constructor, either recur on a smaller input or terminate the recursion with the base case. Another one: start with a seed value, use it to produce the first element of an infinite list, and recur on a modified seed in order to produce the rest of the list. Such a structure is called a recursion scheme. Using higher-order functions to implement those recursion schemes makes your code clearer, faster, and safer. See README for details.
Bindings for Pango, autogenerated by haskell-gi.