Skip to content

Commit f5b11fc

Browse files
authored
Merge pull request #26238 from seliopou/bigstringaf.0.10.0
+bigstringaf.0.10.0
2 parents f26b456 + ea1c964 commit f5b11fc

File tree

1 file changed

+48
-0
lines changed
  • packages/bigstringaf/bigstringaf.0.10.0

1 file changed

+48
-0
lines changed
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
opam-version: "2.0"
2+
maintainer: "Spiros Eliopoulos <[email protected]>"
3+
authors: [ "Spiros Eliopoulos <[email protected]>" ]
4+
license: "BSD-3-clause"
5+
homepage: "https://github.com/inhabitedtype/bigstringaf"
6+
bug-reports: "https://github.com/inhabitedtype/bigstringaf/issues"
7+
dev-repo: "git+https://github.com/inhabitedtype/bigstringaf.git"
8+
build: [
9+
["dune" "subst"] {dev}
10+
[
11+
"dune"
12+
"build"
13+
"-p"
14+
name
15+
"-j"
16+
jobs
17+
"@install"
18+
"@runtest" {with-test}
19+
"@doc" {with-doc}
20+
]
21+
]
22+
depends: [
23+
"dune" {>= "3.0"}
24+
"dune-configurator" {>= "3.0"}
25+
"alcotest" {with-test}
26+
"ocaml" {>= "4.08.0"}
27+
]
28+
conflicts: [
29+
"mirage-xen" {< "6.0.0"}
30+
"ocaml-freestanding"
31+
"js_of_ocaml" {< "3.5.0"}
32+
]
33+
synopsis: "Bigstring intrinsics and fast blits based on memcpy/memmove"
34+
description: """
35+
Bigstring intrinsics and fast blits based on memcpy/memmove
36+
37+
The OCaml compiler has a bunch of intrinsics for Bigstrings, but they're not
38+
widely-known, sometimes misused, and so programs that use Bigstrings are slower
39+
than they have to be. And even if a library got that part right and exposed the
40+
intrinsics properly, the compiler doesn't have any fast blits between
41+
Bigstrings and other string-like types.
42+
43+
So here they are. Go crazy.
44+
"""
45+
url {
46+
src: "https://github.com/inhabitedtype/bigstringaf/archive/0.10.0.tar.gz"
47+
checksum: "md5=be0a44416840852777651150757a0a3b"
48+
}

0 commit comments

Comments
 (0)