base

I'm very much not a serious OCaml:er but when I've dabbled some in it I got the impression that their "standard library" is kind of the de facto standard library. https://github.com/janestreet/base

I don’t know OCaml, or really any language that would help me fully understand the code, but my exposure to OCaml is this stuff, and it looks pretty clean to me. https://github.com/janestreet/base Of course, I haven’t read every file, so maybe I got lucky with my random sampling.

Yes, raising an exn in OCaml is close to jumping to an address stored in a register. https://stackoverflow.com/a/8567429 As a result, raising and catching exns in OCaml is cheap. List.fold_until in Base, for example, is implemented with exceptions: https://github.com/janestreet/base/blob/ae169dc8097b3da8e99d... (With_return is internally implemented by raising an exception in a try-with.) Implementations of functional programming languages often have powerful, yet fast!, non-local control-flow primitives. GHC recently sprouted delimited continuations (https://ghc.gitlab.haskell.org/ghc/doc/users_guide/9.6.1-not...), for example, and Lisps have had that for much longer. It's easy to program in an imperative language for a long time and think that straight-line control flow is the end-all, be-all for performance—but it doesn't have to be th

This delimiter first pattern is used a lot in Ocaml code as well: Records: https://github.com/janestreet/base/blob/master/src/avltree.m... If statements: https://github.com/janestreet/base/blob/master/src/string.ml... Lists: https://github.com/janestreet/base/blob/master/src/string.ml... Function calls: https://github.com/janestreet/base/blob/master/src/string.ml... Type definitions: https://github.com/janestreet/base/blob/master/src/array.ml#... It's not always used, shorter snippets tend to be all on one line.

Base[1] is a good candidate for an OCaml standard library. It's got tons of functionality, results in binaries with small footprints, is cross-platform, and has a fairly stable API. It's also code that has been and continues to be battle tested every day in production systems at Jane Street. I'm biased, as I'm one of the maintainers, but trust me it's good, it's good. [1]: https://github.com/janestreet/base

Someone else mentioned pandas and AQR; I'll also mention BeakerX (Beaker Notebook) which was developed by Two Sigma: https://github.com/twosigma/beakerx You can read more about it here, too: http://beakernotebook.com Jane Street is also pretty awesome - they open sourced their in-house standard library for OCaml, called Base: https://github.com/janestreet/base (they use a lot of OCaml).

Oh, great, yet another library of data structures that introduce incompatible abstractions with both the standard library and the 3 other big libraries of data structures[1,2,3], that is exactly what the OCaml ecosystem needs! :D More seriously, though, at least the naming convention is consistent. It looks a bit heavy on signature-indirection. I would really prefer if they used a standard iterator (gen[5] and sequence[6], for example, or the future one in the stdlib[7]) and settled for one serialization method (such as sexp) and get formatters everywhere. Also, please use ocamldoc or odoc[4] for your documentation. The one generated here is really terrible, even for OCam^W Reason standards. [1]: https://github.com/c-cube/ocaml-containers/ [2]: http://batteries.forge.ocamlcore.org/ [3]: https://github.com/janestreet/base [4]: https://gith