Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jeremie Dimino <jdimino@janestreet.com>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>,
	"ocaml-core@googlegroups.com" <ocaml-core@googlegroups.com>
Subject: Re: [Caml-list] [ANN] Base, Stdio and Jbuilder 0.1.alpha1
Date: Mon, 5 Dec 2016 00:07:53 +0100	[thread overview]
Message-ID: <CANhEzE7B6VsR8KucLeFwXFiSwNe+AQn6VH7NJsAKb=komZ0Dfg@mail.gmail.com> (raw)
In-Reply-To: <86mvgbemva.fsf@gmail.com>

On Sun, Dec 4, 2016 at 4:26 PM, Malcolm Matalka <mmatalka@gmail.com> wrote:
> What's the relationship between Base and Core?  is this another std
> library in the mix or does it replace Core as a stdlib alternative?

Core is a richer stdlib that supersedes Base. More precisely,
Core_kernel supersedes Base and Core supersedes Core_kernel.
Core_kernel adds bin_prot as well as some other features that are not
necessarily as general purpose than what is in Base. Core adds less
portable features and depends on Unix.

But the main difference between Base and Core_kernel is that Base
comes first in the dependency graph. In particular, we can't use
Core_kernel in sexplib, bin_prot or any ppx rewriter used in
Core_kernel. As a result we end up reimplementing the same functions
over and over again. Moreover improvements to Core_kernel don't
benefit sexplib or bin_prot. Now everything has the same base.

Given that Base has much less dependencies than Core_kernel, it should
also be more attractive to people who want to keep a low number of
dependencies.

-- 
Jeremie

      reply	other threads:[~2016-12-04 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04  7:58 Jeremie Dimino
2016-12-04 15:26 ` Malcolm Matalka
2016-12-04 23:07   ` Jeremie Dimino [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANhEzE7B6VsR8KucLeFwXFiSwNe+AQn6VH7NJsAKb=komZ0Dfg@mail.gmail.com' \
    --to=jdimino@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=mmatalka@gmail.com \
    --cc=ocaml-core@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox