From: Lindsey Kuper <icfp.publicity@googlemail.com>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] Deadline extended: Commercial Users of Functional Programming Call For Tutorials
Date: Thu, 30 Jun 2016 19:12:13 -0700 [thread overview]
Message-ID: <CAAmpXiiEYOeox+GTAH-QPOAS4xBubtEgMpLMysMb_rats2gwvA@mail.gmail.com> (raw)
The 2016 Commercial Users of Functional Programming (CUFP) call for
tutorials have passed the initial deadlines, but we have more seat for
tutors.
CUFP tutorial is a good opportunity if you have some idea you want to
spread to the real world, say, your favorite programming language
(Clojure, Erlang, F#, F*, Haskell, ML, OCaml, Scala, Scheme...),
concepts (e.g. Lens, Liquid-Haskell, Proof Assistance, ...),
applications (Web, high-performance computing, finance...,) tools and
techniques (QuickCheck, Elm, ...), or theories.
If you are interested, we kindly invite you to submit a proposal for
the Call For Tutorials from here:
http://cufp.org/2016/call-for-tutorials.html , before July 3rd.
If you have any questions, please do not hesitate to contact us:
Roman Gonzalez: roman@unbounce.com
Takayuki Muranushi: muranushi@gmail.com
best regards,
Takayuki
reply other threads:[~2016-07-01 2:12 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=CAAmpXiiEYOeox+GTAH-QPOAS4xBubtEgMpLMysMb_rats2gwvA@mail.gmail.com \
--to=icfp.publicity@googlemail.com \
--cc=caml-list@inria.fr \
--cc=lindsey@composition.al \
/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).