-
Notifications
You must be signed in to change notification settings - Fork 1.1k
/
opam
40 lines (39 loc) · 1.43 KB
/
opam
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
opam-version: "2.0"
synopsis: "Interfaces for common design patterns (LWT implementation)"
maintainer: "Dorian Peake <dorian@vereia.com>"
authors: "Dorian Peake <dorian@vereia.com>"
homepage: "https://github.com/dozzman/interface-prime"
bug-reports: "https://github.com/dozzman/interface-prime/issues"
tags: [
"interface"
"monad"
"io"
"lwt"
]
depends: [
"ocaml" {>= "4.03"}
"dune" {>= "1.6.2"}
"lwt" {>= "4.1.0"}
"interface-prime" {>= "0.1"}
]
build: [
["dune" "build" "-p" name "-j" jobs]
]
description: """
Interface' (pron. Interface Prime) provides an abstraction for common design patterns
(e.g. monads) which can be implemented by your favourite libraries (e.g. lwt and async) to
reduce the coupling between your code and your dependencies.
**Whats the point?**
I've seen in many libraries the redefininition the same standard functions for monadic
operations, e.g. bind/(>>=), fmap/(>|=)/(>>|). To simplify this NxN problem, Interface'
aims to act as an abstraction over common design patterns like monads to allow a bit more
flexibility between the code you write and the libraries you use.
"""
dev-repo: "git+https://github.com:dozzman/interface-prime.git"
url {
src: "https://github.com/dozzman/interface-prime/archive/0.1.tar.gz"
checksum: [
"md5=9c4116cf209faab28cbc8b932ee19379"
"sha512=d4a118fb947baf2b99e9815b34252132d6e5bd3c9f30cb27c58438dd173460bda9815f98e795655e27c50b177dab4cbcf88eae1d07fda25a96767c6b5feb703e"
]
}