From: Taro Sekiyama <ryukilon@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] FLOPS 2022: the 16th International Symposium on Functional and Logic Programming: Call For Participation & Workshop talk proposals
Date: Tue, 26 Apr 2022 00:58:08 +0900 [thread overview]
Message-ID: <77f2f699-9ef2-27f5-fd8e-8211bddf8e5c@gmail.com> (raw)
============================================================================
Call For Participation & Workshop talk proposals (extended)
FLOPS 2022: 16th International Symposium on Functional and Logic Programming
============================================================================
In-Cooperation with ACM SIGPLAN
May 10-12, 2022, Online
Registration is open for FLOPS 2022.
https://conf.researchr.org/attending/flops-2022/registration
Deadlines for registration are:
(Early) 27 April, 2022, 23:59 (UTC)
(Late) 5 May, 2022, 23:59 (UTC)
*** Call for talk proposals: AiDL 2022 ***
An extra workshop, AiDL 2022 (Workshop on Advances in Declarative Languages),
will be held in hybrid (online / physical) format in Kyoto, Japan.
Venue: Hybrid (Online / RIMS, Kyoto University, Japan)
Talk proposal deadline (extended): April 30, 2022 (AoE)
Details:
https://conf.researchr.org/track/flops-2022/aidl-2022
*** Venue / Dates for the extra workshop ***
This extra event will take place early afternoon (UTC+9), 10-12 May at the
venue, RIMS - Research Institute for Mathematical Sciences, Kyoto
University, Japan, without any interference with the main FLOPS conference
slots, and remote participants are able to attend via Zoom.
*** FLOPS 2022 Accepted Papers ***
The list of FLOPS 2022 accepted papers is at
https://conf.researchr.org/track/flops-2022/flops-2022-papers#event-overview
*** FLOPS 2022 Invited Speakers ***
Lindsey Kuper (University of California at Santa Cruz)
Akimasa Morihata (University of Tokyo)
Peter J. Stuckey (Monash University)
*** FLOPS 2022 Program Committee ***
Andreas Abel Gothenburg University, Sweden
Elvira Albert Universidad Complutense de Madrid
Nada Amin Harvard Universuty, USA
Davide Ancona Univ. Genova, Italy
William Byrd University of Alabama, USA
Matteo Cimini UMass Lowell, USA
Youyou Cong Tokyo Institute of Technology, Japan
Robert Glück University of Copenhagen, Denmark
Makoto Hamana Gunma University, Japan
Michael Hanus Kiel University (co-chair)
Zhenjiang Hu Peking University, China
Atsushi Igarashi Kyoto University, Japan (co-chair)
Ekaterina Komendantskaya Heriot-Watt University, UK
Shin-Cheng Mu Academia Sinica, Taiwan
Koko Muroya Kyoto University, Japan
Klaus Ostermann University of Tuebingen, Germany
Ricardo Rocha University of Porto, Portugal
Tom Schrijvers KU Leuven, Belgium
Harald Sondergaard University of Melbourne, Australia
Hiroshi Unno University of Tsukuba, Japan
Niki Vazou IMDEA, Spain
Janis Voigtlaender University of Duisburg-Essen, Germany
Nicolas Wu Imperial College, UK
Ningning Xie University of Hong Kong, China
Jeremy Yallop University of Cambridge, UK
Neng-Fa Zhou City University of New York, USA
*** FLOPS 2022 Organizers ***
Michael Hanus Kiel University, Germany (PC Co-Chair)
Atsushi Igarashi Kyoto University, Japan (PC Co-Chair, General Chair)
Keigo Imai Gifu University, Japan (Local Co-Chair)
Taro Sekiyama National Institute of Informatics, Japan (Local Co-Chair)
reply other threads:[~2022-04-25 15:58 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=77f2f699-9ef2-27f5-fd8e-8211bddf8e5c@gmail.com \
--to=ryukilon@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