caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anton Bachin <antronbachin@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Human-friendly Lwt: documenting and refactoring the Lwt core
Date: Mon, 15 May 2017 11:00:18 -0400	[thread overview]
Message-ID: <D48E2D51-8B26-4F7E-A072-115BC301D46E@gmail.com> (raw)

Greetings everyone,

Lwt is making an effort to become more reader- and contributor-friendly.

  https://github.com/ocsigen/lwt/pull/354


To summarize, from the PR: the core, lwt.ml, has been reorganized to
make it more readable. It has been equipped with thorough comments,
including a friendly overview of all concepts used by the core.

We hope this change opens Lwt up to more contributions of all kinds. It
should unblock major upcoming work, such as porting Lwt to multicore
effects. Understanding Lwt better also makes it possible to write the
much-promised new manual.

The new Lwt core is meant to be a permanent work in progress: if you
don't understand it, or find that something in it is *still* written in
a confusing way, please ask/let the Lwt maintainers know. We *want* to
help readers understand, and to improve that code! And, anyway, your
query will very likely teach *us* something.


Any review of the PR would be very helpful, to Lwt and to all of its
users – even if you read only to find typos. Also, if you have access to
a stress test, it would be very useful to put the refactored core
through the paces. There are instructions at the bottom of the PR. If
the stress test is open source, maybe we can use it as a guide for
writing a stress test specifically for Lwt, because Lwt really needs to
have at least one of those.


Happy concurrent programming,
Anton


                 reply	other threads:[~2017-05-15 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=D48E2D51-8B26-4F7E-A072-115BC301D46E@gmail.com \
    --to=antronbachin@gmail.com \
    --cc=caml-list@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).