From: "Román González" <roman@unbounce.com>
To: caml-list@inria.fr
Subject: [Caml-list] CUFP 2016 Call for Tutorials
Date: Tue, 14 Jun 2016 06:42:40 +0000 [thread overview]
Message-ID: <CAArPO0Uxm8stx_fKOXwW+qt=GO2m+kcPZAOmegwCnACe2KnQVQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Hi all,
The Commercial Users of Functional Programming (CUFP) 2016 has its Call for
Tutorials open for submission.
CUFP 2016 is being held in the historic city of Nara, Japan. The conference
is devoted to showcase the state of the art of Functional Programming on
industrial settings. This conference is co-located with the International
Conference of Functional Programming (ICFP).
We're looking for tutors that would like to host workshops on on the
following themes:
- Introductions to functional programming languages. In the past we have
had sessions of Clojure, Erlang, F#, F*, Haskell, ML, OCaml, Scala, Scheme
and others.
- Advanced programming languages, concepts and applications (e.g. Lens,
Liquid-Haskell, Agda, Idris, etc.)
- Applying functional programming in particular areas, including Web,
high-performance computing, finance.
- Tools and techniques supporting state of the art functional programming.
In the past we have had tutorials on QuickCheck, Elm and others.
- Theory. Type theory, category theory, abstract algebra, ongoing or new
research, and anything useful or interesting to functional programmers.
If you'd like to submit a proposal, just fill this form
http://goo.gl/forms/qoyK9qYPZhiDPSzO2.
More info can be found at http://cufp.org/2016/call-for-tutorials.html
Regards,
Roman Gonzalez.
[-- Attachment #2: Type: text/html, Size: 5206 bytes --]
reply other threads:[~2016-06-14 6:42 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='CAArPO0Uxm8stx_fKOXwW+qt=GO2m+kcPZAOmegwCnACe2KnQVQ@mail.gmail.com' \
--to=roman@unbounce.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).