From: Thomas Blanc <thomas.blanc@ocamlpro.com>
To: caml-list@inria.fr
Subject: [Caml-list] OCamlPro cheat-sheets updates
Date: Tue, 17 Sep 2019 14:32:30 +0200 [thread overview]
Message-ID: <25b60c50-b961-c883-339c-a0012bc107b9@ocamlpro.com> (raw)
Dear OCaml users,
It is our pleasure to announce the release of our up-to-date
cheat-sheets for the OCaml language and standard library. Our original
cheat-sheets were published in 2011, and as you know there has been
quite a few changes in the language, library and ecosystem overall. See
http://www.ocamlpro.com/2019/09/13/updated-cheat-sheets-ocaml-language-and-ocaml-standard-library/
for details.
Links:
* OCaml language (pdf, 1 page):
http://www.ocamlpro.com/wp-content/uploads/2019/09/ocaml-lang.pdf
* OCaml stdlib (pdf, 2 pages):
http://www.ocamlpro.com/wp-content/uploads/2019/09/ocaml-stdlib.pdf
* Sources: https://github.com/OCamlPro/ocaml-cheat-sheets
Comments and contributions on Github are welcome. Special thanks to
Hannes Mehnert for his lightning fast bug-reporting and Fourchaux for
his keen spelling eye.
As you can see, our Github repository contains not-yet-updated
cheat-sheets. Stay tuned for coming updates! Obviously, our opam
cheat-sheet is already in writing by the greatest opam experts you can
find. We also wish to make sheets for Lwt, Core, Dune, ppx - any
suggestions are welcome.
Happy hacking!
--
Thomas Blanc
OCamlPRO SAS
PS: if you're curious about what we've been doing lately, check out our blogpotst:
http://www.ocamlpro.com/2019/08/30/ocamlpros-compiler-team-work-update/
http://www.ocamlpro.com/2019/07/11/opam-2-0-5-release/
http://www.ocamlpro.com/2019/07/09/alt-ergo-participation-to-the-smt-comp-2019/
next reply other threads:[~2019-09-17 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 12:32 Thomas Blanc [this message]
2019-09-17 16:17 ` Oliver Bandel
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=25b60c50-b961-c883-339c-a0012bc107b9@ocamlpro.com \
--to=thomas.blanc@ocamlpro.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).