Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Taro Sekiyama <ryukilon@gmail.com>
To: caml-list@inria.fr, types-announce@lists.seas.upenn.edu
Subject: [Caml-list] [CFP] HOPE'26: ACM SIGPLAN Workshop on Higher-Order Programming with Effects
Date: Wed, 29 Apr 2026 18:27:25 +0900	[thread overview]
Message-ID: <CAH67BN5WbyV6tmNQ2NemFbGQwJpvbBvRcmXtftdLGCgQGXXEOQ@mail.gmail.com> (raw)

TL;DR:
Talk proposal deadline for HOPE 2026 is on May 29, 2026.
This year, the workshop will be co-located with ICFP'26 (Indiana, US)
and FW'26 (Paris, France)
----------------------------------------------------------------------

                             HOPE 2026

            The 14th ACM SIGPLAN Workshop on
            Higher-Order Programming with Effects

                          August 24, 2026
                  (the day before ICFP 2026)

          https://icfp26.sigplan.org/home/hope-2026


HOPE 2026 aims to bring together researchers interested in the design,
semantics, implementation, and verification of higher-order effectful
programs. It will be *informal*, consisting of invited talks, contributed talks
on work in progress, and open-ended discussion sessions.

----------------------
Call for Talk Proposals
-----------------------

We solicit proposals for contributed talks. We recommend preparing proposals of
at most 2 pages excluding references, in either plain text or PDF
format. However, we will accept longer proposals or submissions to other
conferences, under the understanding that PC members are only expected to read
the first two pages of such longer submissions. When submitting talk proposals,
authors should specify how long a talk the speaker wishes to give. By default,
contributed talks will be 30 minutes long, but proposals for shorter or longer
talks will also be considered. Speakers may also submit supplementary material
(e.g. a full paper, talk slides) if they desire, which PC members are free (but
not expected) to read.

We are interested in talks on all topics related to the interaction of
higher-order programming and computational effects. Talks about work
in progress are particularly encouraged. If you have any questions
about the relevance of a particular topic, please contact the PC
chairs, Taro Sekiyama (tsekiyama@acm.org) and Francesco Gavazzo
(francesco.gavazzo@unipd.it).

Important Note: HOPE’26 will be co-located with ICFP’26
(https://icfp26.sigplan.org/) and FW’26
(https://www.irif.fr/~scherer/events/fpw-2026/announce.html).
Presenters can choose either event to attend in-person. We also
encourage remote participation and will support remote presentations.

Deadline for talk proposals: May 29, 2026 (Friday)

Notification of acceptance:  June 26, 2026 (Friday)

Workshop:  August 24, 2026, Indiana, United States & Paris, France (tentatively)

The submission website is now open:

          https://hope26.hotcrp.com

---------------------
Workshop Organization
---------------------

Program Committee:

Yuyan Bao (Augusta University)
Raphaëlle Crubillé (Aix-Marseille University)
Francesco Dagnino (University of Genova)
Elena di Lavore (University of Oxford)
Francesco Gavazzo (University of Padua)
Cristina Matache (University of Edinburgh)
Ken Sakayori (The University of Tokyo)
Taro Sekiyama (National Institute of Informatics)
Dario Stein (Radboud University)
Niels Voorneveld (Cybernetica)
Zhixuan Yang (University of Exeter)

---------------------
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 and handlers, 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.

We want HOPE to be as informal and interactive as possible. The program will
thus involve a combination of invited talks, contributed talks about work in
progress, and open-ended discussion sessions. There will be no published
proceedings, but participants will be invited to submit working documents, talk
slides, etc., to be made available online.

-- 
Taro Sekiyama

                 reply	other threads:[~2026-04-29  9:28 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=CAH67BN5WbyV6tmNQ2NemFbGQwJpvbBvRcmXtftdLGCgQGXXEOQ@mail.gmail.com \
    --to=ryukilon@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=types-announce@lists.seas.upenn.edu \
    /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