From: "François Pottier" <francois.pottier@inria.fr>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Call for Participation: Higher-Order Programming with Effects, HOPE 2017
Date: Wed, 12 Jul 2017 10:50:24 +0200 [thread overview]
Message-ID: <a71c638a-3455-f484-52d8-8d6df52629ba@inria.fr> (raw)
One-liner: the list of accepted talks for HOPE 2017 is now online!
------------------------------------------------------------------------------
CALL FOR PARTICIPATION
HOPE 2017
The 6th ACM SIGPLAN Workshop on
Higher-Order Programming with Effects
September 3, 2017
Oxford, United Kingdom
(the day before ICFP 2017)
http://icfp17.sigplan.org/track/hope-2017-papers#event-overview
------------------------------------------------------------------------------
The HOPE workshop series are intended to bring together researchers
interested
in the design, semantics, implementation, and verification of higher-order
effectful programs. They are informal, consisting of invited talks,
contributed talks on work in progress, and open-ended discussion sessions.
They are dedicated to John Reynolds, whose work is an inspiration to us all.
The 6th ACM SIGPLAN Workshop on Higher-Order Programming with Effects will
take place on Sunday, September 3, 2017, that is, the day before ICFP 2017,
in Oxford, United Kingdom.
# Goals of the Workshop
A recurring theme in many papers at ICFP, and in the research of many ICFP
attendees, is the interaction of higher-order programming with various kinds
of effects: storage effects, I/O, control effects, concurrency, etc. While
effects are of critical importance in many applications, they also make code
harder to build, maintain, and reason about. Higher-order languages (both
functional and object-oriented) provide a variety of abstraction
mechanisms to
help "tame" or "encapsulate" effects (e.g. monads, ADTs, ownership types,
typestate, first-class events, transactions, Hoare Type Theory, session
types,
substructural and region-based type systems), and a number of different
semantic models and verification technologies have been developed in
order to
codify and exploit the benefits of this encapsulation (e.g. bisimulations,
step-indexed Kripke logical relations, higher-order separation logic, game
semantics, various modal logics). But there remain many open problems,
and the
field is highly active.
The goal of the HOPE workshop is to bring researchers from a variety of
different backgrounds and perspectives together to exchange new and exciting
ideas concerning the design, semantics, implementation, and verification of
higher-order effectful programs.
# Important Dates
* Workshop: September 3, 2017 (Sunday)
# Accepted Talks
http://icfp17.sigplan.org/track/hope-2017-papers#event-overview
# Workshop Organization
Program Co-Chairs:
François Pottier (Inria Paris)
Aleks Nanevski (IMDEA Software Institute)
Program Committee:
Edwin Brady University of St Andrews
Pierre-Évariste Dagand LIP6/CNRS
Atsushi Igarashi Kyoto University
Robbert Krebbers Delft University of Technology
Vivek Nigam Federal University of Paraíba
Matija Pretnar University of Ljubljana
Azalea Raad Imperial College London
Aseem Rastogi Microsoft Research
Filip Sieczkowski University of Wrocław
Niki Vazou University of Maryland
reply other threads:[~2017-07-12 8:50 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=a71c638a-3455-f484-52d8-8d6df52629ba@inria.fr \
--to=francois.pottier@inria.fr \
--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