Skip to content

Commit

Permalink
move to opam2
Browse files Browse the repository at this point in the history
  • Loading branch information
hannesm committed Oct 22, 2018
1 parent cb4a9c0 commit 8d607a0
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 16 deletions.
9 changes: 0 additions & 9 deletions bigstringaf.descr

This file was deleted.

24 changes: 17 additions & 7 deletions bigstringaf.opam
Original file line number Diff line number Diff line change
@@ -1,24 +1,34 @@
opam-version: "1.2"
opam-version: "2.0"
maintainer: "Spiros Eliopoulos <[email protected]>"
authors: [ "Spiros Eliopoulos <[email protected]>" ]
license: "BSD-3-clause"
homepage: "https://github.com/inhabitedtype/bigstringaf"
bug-reports: "https://github.com/inhabitedtype/bigstringaf/issues"
dev-repo: "https://github.com/inhabitedtype/bigstringaf.git"
dev-repo: "git+https://github.com/inhabitedtype/bigstringaf.git"
build: [
["jbuilder" "subst" "-p" name] {pinned}
["jbuilder" "build" "-p" name "-j" jobs]
]
build-test: [
["jbuilder" "runtest" "-p" name]
["jbuilder" "runtest" "-p" name] {with-test}
]
depends: [
"jbuilder" {build & >= "1.0+beta10"}
"alcotest" {test}
"alcotest" {with-test}
"base-bigarray"
"ocaml" {>= "4.03.0"}
]
depopts: [
"mirage-xen-posix"
"ocaml-freestanding"
]
available: [ ocaml-version >= "4.03.0" ]
synopsis: "Bigstring intrinsics and fast blits based on memcpy/memmove"
description: """
Bigstring intrinsics and fast blits based on memcpy/memmove

The OCaml compiler has a bunch of intrinsics for Bigstrings, but they're not
widely-known, sometimes misused, and so programs that use Bigstrings are slower
than they have to be. And even if a library got that part right and exposed the
intrinsics properly, the compiler doesn't have any fast blits between
Bigstrings and other string-like types.

So here they are. Go crazy.
"""

0 comments on commit 8d607a0

Please sign in to comment.