You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
synopsis="An interface for a handler-independent, typeclass-based effect system.";
22
+
description="This library provides definitions for CEPs (classy-effects protocols) to standardize and unify\nthe definition of effects in Haskell in a backend-library-agnostic manner. It also includes\nseveral standard effect definitions defined in compliance with CEPs, and Template Haskell\nfunctions to automatically make type classes conform to CEPs as effect classes.\n\nPlease refer\nto [CEPs](https://github.com/sayo-hs/classy-effects/blob/master/CEPs/README.md) for details.\n\nThe Template Haskell functions are re-exported\nfrom the [classy-effects-th](https://hackage.haskell.org/package/classy-effects-th) package,\nwhile the fundamental definitions are re-exported\nfrom the [classy-effects-base](https://hackage.haskell.org/package/classy-effects-base)\npackage.\n\n__This 'classy-effects' project was abandoned due to the discovery of fundamental difficulties.__\nThe reasons are as follows: <https://github.com/orgs/sayo-hs/projects/4?pane=issue&itemId=48547880>\n__As an alternative, consider using 'sayo-hs/data-effects', a GADTs-based common effect representation foundation:__\n<https://github.com/sayo-hs/data-effects>.";
synopsis="An interface for a handler-independent, typeclass-based effect system.";
22
+
description="This library provides definitions for CEPs (classy-effects protocols) to standardize and unify\nthe definition of effects in Haskell in a backend-library-agnostic manner. Please refer\nto [CEPs](https://github.com/sayo-hs/classy-effects/blob/master/CEPs/README.md) for details.\n\nThis library provides only the fundamental definitions for classy-effects. Please also refer to\nthe [classy-effects](https://hackage.haskell.org/package/classy-effects) package, which offers\nstandard effect definitions compliant with CEPs, and\nthe [classy-effects-th](https://hackage.haskell.org/package/classy-effects-th) package, which\nenables automatic compliance with CEPs.\n\n__This 'classy-effects' project was abandoned due to the discovery of fundamental difficulties.__\nThe reasons are as follows: <https://github.com/orgs/sayo-hs/projects/4?pane=issue&itemId=48547880>\n__As an alternative, consider using 'sayo-hs/data-effects', a GADTs-based common effect representation foundation:__\n<https://github.com/sayo-hs/data-effects>.";
synopsis="Automatic compliance with the classy-effects protocols";
22
+
description="This package provides Template Haskell functions that enable automatic compliance with CEPs\n(classy-effects protocols), offering a unified framework for defining effects in Haskell.\n\nCEPs aim to standardize and unify the definition of effects in Haskell in a\nbackend-library-agnostic manner. Please refer\nto [CEPs](https://github.com/sayo-hs/classy-effects/blob/master/CEPs/README.md) for details.\n\nPlease also refer to the [classy-effects](https://hackage.haskell.org/package/classy-effects)\npackage, which offers standard effect definitions compliant with CEPs.\n\n__This 'classy-effects' project was abandoned due to the discovery of fundamental difficulties.__\nThe reasons are as follows: <https://github.com/orgs/sayo-hs/projects/4?pane=issue&itemId=48547880>\n__As an alternative, consider using 'sayo-hs/data-effects', a GADTs-based common effect representation foundation:__\n<https://github.com/sayo-hs/data-effects>.";
synopsis="Client library for the Redis datastore: supports full command set,\npipelining.";
22
+
description="Redis is an open source, advanced key-value store. It is often referred to\nas a data structure server since keys can contain strings, hashes, lists,\nsets and sorted sets. This library is a Haskell client for the Redis\ndatastore. Compared to other Haskell client libraries it has some\nadvantages:\n\n[Compatibility with Latest Stable Redis:] Hedis is intended\nto be used with the latest stable version of Redis (currently 5.0).\nMost redis commands (<http://redis.io/commands>) are available as\nhaskell functions, although MONITOR and SYNC are intentionally\nomitted. Additionally, a low-level API is\nexposed that makes it easy for the library user to implement further\ncommands, such as new commands from an experimental Redis version.\n\n[Automatic Optimal Pipelining:] Commands are pipelined\n(<http://redis.io/topics/pipelining>) as much as possible without any\nwork by the user. See\n<http://informatikr.com/2012/redis-pipelining.html> for a\ntechnical explanation of automatic optimal pipelining.\n\n[Enforced Pub\\/Sub semantics:] When subscribed to the Redis Pub\\/Sub server\n(<http://redis.io/topics/pubsub>), clients are not allowed to issue\ncommands other than subscribing to or unsubscribing from channels. This\nlibrary uses the type system to enforce the correct behavior.\n\n[Connect via TCP or Unix Domain Socket:] TCP sockets are the default way to\nconnect to a Redis server. For connections to a server on the same\nmachine, Unix domain sockets offer higher performance than the standard\nTCP connection.\n\nFor detailed documentation, see the \"Database.Redis\" module.\n";
0 commit comments