From: Runhang Li <marklrh@gmail.com>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] CUFP 2017 Call for Tutorials
Date: Mon, 24 Apr 2017 23:46:23 -0700 [thread overview]
Message-ID: <AFAB5DE3-E177-41DF-84AE-07248A6BBBE7@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
Call for tutorials
Commercial Users of Functional Programming (CUFP) 2017
September 7th-9th, 2017, Oxford, United Kingdom
Co-located with International Conference on Functional Programming (ICFP)
Dear fellow camels,
Commercial Users of Functional Programming (CUFP) 2017 is now seeking
tutorials proposals.
Co-located with International Conference on Functional Programming (ICFP),
Commercial Users of Functional Programming (CUFP) will take place in Oxford, U.K.
from 7th to 9th of September, 2017. CUFP is devoted to showcase the state of
the art of functional programming in industrial settings.
We are looking for tutors who would like to host half-day tutorial sessions
of the following topics:
* Introductions to functional programming languages, e.g., Haskell, OCaml,
Scala, F#, Scheme, Erlang, Clojure.
* Advanced programming languages, concepts, or applications, e.g., Agda, Idris,
F*, Coq, Eff.
* Applications of functional languages in particular areas, including web,
high-performance computing, and finance.
* Tools and techniques supporting state of the art functional programming, e.g.,
ReasonML, TypeScript, Elm, QuickCheck, FlowType.
* Theory. Type theory, category theory, abstract algebra, ongoing or new
research, or anything useful or interesting to functional programmers.
**Proposal submission deadline is May 25th**
Details can be found at: http://cufp.org/2017/call-for-tutorials.html
Kindly,
Runhang Li, CUFP 2017 tutorials co-chair
[-- Attachment #2: Type: text/html, Size: 4542 bytes --]
reply other threads:[~2017-04-25 6:46 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=AFAB5DE3-E177-41DF-84AE-07248A6BBBE7@gmail.com \
--to=marklrh@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).