CFP: Haskell Symposium 2023
Trevor McDonell <[email protected]> Fri, 24 Mar 2023 11:28:59 +0100
| Newsgroups | gmane.comp.lang.haskell.glasgow.user |
|---|---|
| Message-ID | <CAFcD48UQTBgwiFJeuUG=zeFiBU8-bBpGbRyAHxU+Y=ZDmNRb+Q@mail.gmail.com> |
--===============7438588878843049296==
Content-Type: multipart/alternative; boundary="00000000000024aecf05f7a2dd11"
--00000000000024aecf05f7a2dd11
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
ACM SIGPLAN CALL FOR
SUBMISSIONS
Haskell Symposium 2023
Seattle, WA, USA
Fri 8 -- Sat 9 September, 2023
http://www.haskell.org/haskell-symposium/2023/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
The ACM SIGPLAN Haskell Symposium 2023 will be co-located with the 2023
International Conference on Functional Programming (ICFP).
As with last year, Haskell'23 will use a single-track submission process.
That
is, we will only have the regular track and no early track.
The Haskell Symposium presents original research on Haskell, discusses
practical
experience and future development of the language, and promotes other forms
of
declarative programming.
Topics of interest include:
* Language design, with a focus on possible extensions and modifications
of
Haskell as well as critical discussions of the status quo;
* Theory, such as formal semantics of the present language or future
extensions, type systems, effects, metatheory, and foundations for
program
analysis and transformation;
* Implementations, including program analysis and transformation, static
and
dynamic compilation for sequential, parallel, and distributed
architectures,
memory management, as well as foreign function and component interfaces=
;
* Libraries, that demonstrate new ideas or techniques for functional
programming in Haskell;
* Tools, such as profilers, tracers, debuggers, preprocessors, and testin=
g
tools;
* Applications, to scientific and symbolic computing, databases,
multimedia,
telecommunication, the web, and so forth;
* Functional Pearls, being elegant and instructive programming examples;
* Experience Reports, to document general practice and experience in
education, industry, or other contexts;
* Tutorials, to document how to use a particular language feature,
programming
technique, tool or library within the Haskell ecosystem;
* System Demonstrations, based on running software rather than novel
research
results.
Regular papers should explain their research contributions in both general
and
technical terms, identifying what has been accomplished, explaining why it
is
significant, and relating it to previous work, and to other languages where
appropriate.
Experience reports and functional pearls need not necessarily report
original
academic research results. For example, they may instead report reusable
programming idioms, elegant ways to approach a problem, or practical
experience
that will be useful to other users, implementers, or researchers. The key
criterion for such a paper is that it makes a contribution from which other
Haskellers can benefit. It is not enough simply to describe a standard
solution
to a standard programming problem, or report on experience where you used
Haskell in the standard way and achieved the result you were expecting.
Like an experience report and a functional pearl, tutorials should make a
contribution from which other Haskellers can benefit. What distinguishes a
tutorial is that its focus is on explaining an aspect of the Haskell
language
and/or ecosystem in a way that is generally useful to a Haskell audience.
Tutorials for many such topics can be found online; the distinction here is
that
by writing it up for formal review it will be vetted by experts and formall=
y
published.
System demonstrations should summarize the system capabilities that would b=
e
demonstrated. The proposals will be judged on whether the ensuing session i=
s
likely to be important and interesting to the Haskell community at large,
whether on grounds academic or industrial, theoretical or practical,
technical,
social or artistic. Please contact the program chair with any questions
about
the relevance of a proposal.
If your contribution is not a research paper, please mark the title of your
experience report, functional pearl, tutorial or system demonstration as
such,
by supplying a subtitle (Experience Report, Functional Pearl, Tutorial
Paper,
System Demonstration).
Submission Details
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Formatting
----------
Submitted papers should be in portable document format (PDF), formatted
using
the ACM SIGPLAN style guidelines. Authors should use the `acmart` format,
with
the `sigplan` sub-format for ACM proceedings. For details, see:
http://www.sigplan.org/Resources/Author/#acmart-format
It is recommended to use the `review` option when submitting a paper; this
option enables line numbers for easy reference in reviews.
Functional pearls, experience reports, tutorials and demo proposals should
be
labelled clearly as such.
Lightweight Double-blind Reviewing
----------------------------------
Haskell Symposium 2023 will use a lightweight double-blind reviewing
process. To
facilitate this, submitted papers must adhere to two rules:
1. Author names and institutions must be omitted, and
2. References to authors' own related work should be in the third person
(e.g., not "We build on our previous work" but rather "We build on the
work of ").
The purpose of this process is to help the reviewers come to an initial
judgement about the paper without bias, not to make it impossible for them
to
discover the authors if they were to try. Nothing should be done in the
name of
anonymity that weakens the submission or makes the job of reviewing the
paper
more difficult (e.g., important background references should not be omitted
or
anonymised). In addition, authors should feel free to disseminate their
ideas or
draft versions of their paper as they normally would. For instance, authors
may
post drafts of their papers on the web or give talks on their research
ideas.
A reviewer will learn the identity of the author(s) of a paper after a
review is
submitted.
Page Limits
-----------
The length of submissions should not exceed the following limits:
Regular paper: 12 pages
Functional pearl: 12 pages
Tutorial: 12 pages
Experience report: 6 pages
Demo proposal: 2 pages
There is no requirement that all pages are used. For example, a functional
pearl
may be much shorter than 12 pages. In all cases, the list of references is
not
counted against these page limits.
Deadlines
---------
Paper submission: 1 June 2023 (Thu)
Notification: 4 July 2023 (Tue)
Camera ready: 18 July 2023 (Tue)
Deadlines are anywhere on Earth.
Submission
----------
Submissions must adhere to SIGPLAN's republication policy
(http://sigplan.org/Resources/Policies/Republication/), and authors should
be
aware of ACM's policies on plagiarism
(https://www.acm.org/publications/policies/plagiarism). Program Committee
members are allowed to submit papers, but their papers will be held to a
higher
standard.
The paper submission deadline and length limitations are firm. There will
be no
extensions, and papers violating the length limitations will be summarily
rejected.
Papers should be submitted through HotCRP at:
https://haskell23.hotcrp.com/
Improved versions of a paper may be submitted at any point before the
submission
deadline using the same web interface.
Supplementary material: Authors have the option to attach supplementary
material
to a submission, on the understanding that reviewers may choose not to look
at
it. This supplementary material should not be submitted as part of the main
document; instead, it should be uploaded as a separate PDF document or
tarball.
Supplementary material should be uploaded at submission time, not by
providing a
URL in the paper that points to an external repository. Authors can
distinguish
between anonymised and non-anonymised supplementary material. Anonymised
supplementary material will be visible to reviewers immediately;
non-anonymised
supplementary material will be revealed to reviewers only after they have
submitted their review of the paper and learned the identity of the
author(s).
Resubmitted Papers: authors who submit a revised version of a paper that ha=
s
previously been rejected by another conference have the option to attach an
annotated copy of the reviews of their previous submission(s), explaining
how
they have addressed these previous reviews in the present submission. If a
reviewer identifies him/herself as a reviewer of this previous submission
and
wishes to see how his/her comments have been addressed, the conference chai=
r
will communicate to this reviewer the annotated copy of his/her previous
review.
Otherwise, no reviewer will read the annotated copies of the previous
reviews.
Proceedings
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Accepted papers will be included in the ACM Digital Library. Their authors
will
be required to choose one of the following options:
- Author retains copyright of the work and grants ACM a non-exclusive
permission-to-publish license (and, optionally, licenses the work with =
a
Creative Commons license);
- Author retains copyright of the work and grants ACM an exclusive
permission-to-publish license;
- Author transfers copyright of the work to ACM.
For more information, please see ACM Copyright Policy
(http://www.acm.org/publications/policies/copyright-policy) and ACM Author
Rights (http://authors.acm.org/main.html).
Accepted proposals for system demonstrations will be posted on the symposiu=
m
website but not formally published in the proceedings.
Publication date: The official publication date of accepted papers is the
date
the proceedings are made available in the ACM Digital Library. This date
may be
up to two weeks prior to the first day of the conference. The official
publication date affects the deadline for any patent filings related to
published work.
Artefacts
=3D=3D=3D=3D=3D=3D=3D=3D=3D
Authors are encouraged to make auxiliary material (artefacts like source
code,
test data, etc.) available with their paper. Authors can opt to have these
artefacts published alongside their paper in the ACM Digital Library
(copyright
of artefacts remains with the authors). Artefacts must be included as part
of
their submission to HotCRP and should consist of a .zip file containing the
artefact materials, a README explaining the contents of the artefact and
how it
should be used, and a LICENSE file.
If an accepted paper's artefacts are made permanently available for
retrieval in
a publicly accessible archival repository like the ACM Digital Library, tha=
t
paper qualifies for an Artefact badge
(https://www.acm.org/publications/policies/artifact-review-badging).
Program Committee
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Alexander Green Standard Chartered, UK
David Thrane Christiansen The Haskell Foundation, Denmark
Edsko de Vries Well-Typed LLP, Netherlands
Exequiel Rivas Tallinn University of Technology
Facundo Dom=C3=ADnguez Tweag
Florian Zuleger TU Vienna, Austria
Graham Hutton University of Nottingham, UK
Jasper Van der Jeugt Snyk, Switzerland
Jennifer Paykin Intel, USA
Jesper Cockx Delft University of Technology, Netherlands
Jose Nuno Oliveira University of Minho & INESC TEC, Portugal
Michael Sperber Active Group GmbH, Germany
Michel Steuwer University of Edinburgh, UK
Niki Vazou (chair) IMDEA Software Institute, Spain
Rumyana Neykova Brunel University London, UK
Trevor L. McDonell (co-chair) Utrecht University, Netherlands
Ugo Dal Lago University of Bologna, Italy & INRIA, Franc=
e
Wen Kokke University of Edinburgh, UK
Leonidas Lampropoulos University of Maryland, College Park, USA
If you have questions, please contact the chairs at [email protected] an=
d
[email protected].
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
--00000000000024aecf05f7a2dd11
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><font face=3D"monospace">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=C2=A0ACM SIGPLAN=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 CALL FOR SUBMISSIONS<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Haskell S=
ymposium 2023<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Seattle, WA, US=
A<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0Fri 8 -- Sat 9 September, 2023<br><br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.haskell.=
org/haskell-symposium/2023/">http://www.haskell.org/haskell-symposium/2023/=
</a><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>The ACM SIGPLAN Haskell Symposium 2023 w=
ill be co-located with the 2023<br>International Conference on Functional P=
rogramming (ICFP).<br><br>As with last year, Haskell'23 will use a sing=
le-track submission process. That<br>is, we will only have the regular trac=
k and no early track.<br><br>The Haskell Symposium presents original resear=
ch on Haskell, discusses practical<br>experience and future development of =
the language, and promotes other forms of<br>declarative programming.<br><b=
r>Topics of interest include:<br><br>=C2=A0 * Language design, with a focus=
on possible extensions and modifications of<br>=C2=A0 =C2=A0 Haskell as we=
ll as critical discussions of the status quo;<br><br>=C2=A0 * Theory, such =
as formal semantics of the present language or future<br>=C2=A0 =C2=A0 exte=
nsions, type systems, effects, metatheory, and foundations for program<br>=
=C2=A0 =C2=A0 analysis and transformation;<br><br>=C2=A0 * Implementations,=
including program analysis and transformation, static and<br>=C2=A0 =C2=A0=
dynamic compilation for sequential, parallel, and distributed architecture=
s,<br>=C2=A0 =C2=A0 memory management, as well as foreign function and comp=
onent interfaces;<br><br>=C2=A0 * Libraries, that demonstrate new ideas or =
techniques for functional<br>=C2=A0 =C2=A0 programming in Haskell;<br><br>=
=C2=A0 * Tools, such as profilers, tracers, debuggers, preprocessors, and t=
esting<br>=C2=A0 =C2=A0 tools;<br><br>=C2=A0 * Applications, to scientific =
and symbolic computing, databases, multimedia,<br>=C2=A0 =C2=A0 telecommuni=
cation, the web, and so forth;<br><br>=C2=A0 * Functional Pearls, being ele=
gant and instructive programming examples;<br><br>=C2=A0 * Experience Repor=
ts, to document general practice and experience in<br>=C2=A0 =C2=A0 educati=
on, industry, or other contexts;<br><br>=C2=A0 * Tutorials, to document how=
to use a particular language feature, programming<br>=C2=A0 =C2=A0 techniq=
ue, tool or library within the Haskell ecosystem;<br><br>=C2=A0 * System De=
monstrations, based on running software rather than novel research<br>=C2=
=A0 =C2=A0 results.<br><br>Regular papers should explain their research con=
tributions in both general and<br>technical terms, identifying what has bee=
n accomplished, explaining why it is<br>significant, and relating it to pre=
vious work, and to other languages where<br>appropriate.<br><br>Experience =
reports and functional pearls need not necessarily report original<br>acade=
mic research results. For example, they may instead report reusable<br>prog=
ramming idioms, elegant ways to approach a problem, or practical experience=
<br>that will be useful to other users, implementers, or researchers. The k=
ey<br>criterion for such a paper is that it makes a contribution from which=
other<br>Haskellers can benefit. It is not enough simply to describe a sta=
ndard solution<br>to a standard programming problem, or report on experienc=
e where you used<br>Haskell in the standard way and achieved the result you=
were expecting.<br><br>Like an experience report and a functional pearl, t=
utorials should make a<br>contribution from which other Haskellers can bene=
fit. What distinguishes a<br>tutorial is that its focus is on explaining an=
aspect of the Haskell language<br>and/or ecosystem in a way that is genera=
lly useful to a Haskell audience.<br>Tutorials for many such topics can be =
found online; the distinction here is that<br>by writing it up for formal r=
eview it will be vetted by experts and formally<br>published.<br><br>System=
demonstrations should summarize the system capabilities that would be<br>d=
emonstrated. The proposals will be judged on whether the ensuing session is=
<br>likely to be important and interesting to the Haskell community at larg=
e,<br>whether on grounds academic or industrial, theoretical or practical, =
technical,<br>social or artistic. Please contact the program chair with any=
questions about<br>the relevance of a proposal.<br><br>If your contributio=
n is not a research paper, please mark the title of your<br>experience repo=
rt, functional pearl, tutorial or system demonstration as such,<br>by suppl=
ying a subtitle (Experience Report, Functional Pearl, Tutorial Paper,<br>Sy=
stem Demonstration).<br><br>Submission Details<br>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>Formatting<br>----------<br><br>Submi=
tted papers should be in portable document format (PDF), formatted using<br=
>the ACM SIGPLAN style guidelines. Authors should use the `acmart` format, =
with<br>the `sigplan` sub-format for ACM proceedings. For details, see:<br>=
<br>=C2=A0 <a href=3D"http://www.sigplan.org/Resources/Author/#acmart-forma=
t">http://www.sigplan.org/Resources/Author/#acmart-format</a><br><br>It is =
recommended to use the `review` option when submitting a paper; this<br>opt=
ion enables line numbers for easy reference in reviews.<br><br>Functional p=
earls, experience reports, tutorials and demo proposals should be<br>labell=
ed clearly as such.<br><br>Lightweight Double-blind Reviewing<br>----------=
------------------------<br><br>Haskell Symposium 2023 will use a lightweig=
ht double-blind reviewing process. To<br>facilitate this, submitted papers =
must adhere to two rules:<br><br>=C2=A01. Author names and institutions mus=
t be omitted, and<br>=C2=A02. References to authors' own related work s=
hould be in the third person<br>=C2=A0 =C2=A0 (e.g., not "We build on =
our previous work" but rather "We build on the work of ").<b=
r><br>The purpose of this process is to help the reviewers come to an initi=
al<br>judgement about the paper without bias, not to make it impossible for=
them to<br>discover the authors if they were to try. Nothing should be don=
e in the name of<br>anonymity that weakens the submission or makes the job =
of reviewing the paper<br>more difficult (e.g., important background refere=
nces should not be omitted or<br>anonymised). In addition, authors should f=
eel free to disseminate their ideas or<br>draft versions of their paper as =
they normally would. For instance, authors may<br>post drafts of their pape=
rs on the web or give talks on their research ideas.<br><br>A reviewer will=
learn the identity of the author(s) of a paper after a review is<br>submit=
ted.<br><br>Page Limits<br>-----------<br><br>The length of submissions sho=
uld not exceed the following limits:<br><br>Regular paper: =C2=A0 =C2=A0 =
=C2=A012 pages<br>Functional pearl: =C2=A0 12 pages<br>Tutorial: =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 12 pages<br>Experience report: =C2=A0 6 pages<br>D=
emo proposal: =C2=A0 =C2=A0 =C2=A0 2 pages<br><br>There is no requirement t=
hat all pages are used. For example, a functional pearl<br>may be much shor=
ter than 12 pages. In all cases, the list of references is not<br>counted a=
gainst these page limits.<br><br>Deadlines<br>---------<br><br>Paper submis=
sion: =C2=A0 =C2=A0 =C2=A0 =C2=A01 June 2023 =C2=A0 =C2=A0 =C2=A0(Thu)<br>N=
otification: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A04 July 2023 =C2=A0 =
=C2=A0 =C2=A0(Tue)<br>Camera ready: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 18 J=
uly 2023 =C2=A0 =C2=A0 =C2=A0(Tue)<br><br>Deadlines are anywhere on Earth.<=
br><br>Submission<br>----------<br><br>Submissions must adhere to SIGPLAN&#=
39;s republication policy<br>(<a href=3D"http://sigplan.org/Resources/Polic=
ies/Republication/">http://sigplan.org/Resources/Policies/Republication/</a=
>), and authors should be<br>aware of ACM's policies on plagiarism<br>(=
<a href=3D"https://www.acm.org/publications/policies/plagiarism">https://ww=
w.acm.org/publications/policies/plagiarism</a>). Program Committee<br>membe=
rs are allowed to submit papers, but their papers will be held to a higher<=
br>standard.<br><br>The paper submission deadline and length limitations ar=
e firm. There will be no<br>extensions, and papers violating the length lim=
itations will be summarily<br>rejected.<br><br>Papers should be submitted t=
hrough HotCRP at:<br><br>=C2=A0 <a href=3D"https://haskell23.hotcrp.com/">h=
ttps://haskell23.hotcrp.com/</a><br><br>Improved versions of a paper may be=
submitted at any point before the submission<br>deadline using the same we=
b interface.<br><br>Supplementary material: Authors have the option to atta=
ch supplementary material<br>to a submission, on the understanding that rev=
iewers may choose not to look at<br>it. This supplementary material should =
not be submitted as part of the main<br>document; instead, it should be upl=
oaded as a separate PDF document or tarball.<br>Supplementary material shou=
ld be uploaded at submission time, not by providing a<br>URL in the paper t=
hat points to an external repository. Authors can distinguish<br>between an=
onymised and non-anonymised supplementary material. Anonymised<br>supplemen=
tary material will be visible to reviewers immediately; non-anonymised<br>s=
upplementary material will be revealed to reviewers only after they have<br=
>submitted their review of the paper and learned the identity of the author=
(s).<br><br>Resubmitted Papers: authors who submit a revised version of a p=
aper that has<br>previously been rejected by another conference have the op=
tion to attach an<br>annotated copy of the reviews of their previous submis=
sion(s), explaining how<br>they have addressed these previous reviews in th=
e present submission. If a<br>reviewer identifies him/herself as a reviewer=
of this previous submission and<br>wishes to see how his/her comments have=
been addressed, the conference chair<br>will communicate to this reviewer =
the annotated copy of his/her previous review.<br>Otherwise, no reviewer wi=
ll read the annotated copies of the previous reviews.<br><br>Proceedings<br=
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>Accepted papers will be included =
in the ACM Digital Library. Their authors will<br>be required to choose one=
of the following options:<br><br>=C2=A0 - Author retains copyright of the =
work and grants ACM a non-exclusive<br>=C2=A0 =C2=A0 permission-to-publish =
license (and, optionally, licenses the work with a<br>=C2=A0 =C2=A0 Creativ=
e Commons license);<br><br>=C2=A0 - Author retains copyright of the work an=
d grants ACM an exclusive<br>=C2=A0 =C2=A0 permission-to-publish license;<b=
r><br>=C2=A0 - Author transfers copyright of the work to ACM.<br><br>For mo=
re information, please see ACM Copyright Policy<br>(<a href=3D"http://www.a=
cm.org/publications/policies/copyright-policy">http://www.acm.org/publicati=
ons/policies/copyright-policy</a>) and ACM Author<br>Rights (<a href=3D"htt=
p://authors.acm.org/main.html">http://authors.acm.org/main.html</a>).<br><b=
r>Accepted proposals for system demonstrations will be posted on the sympos=
ium<br>website but not formally published in the proceedings.<br><br>Public=
ation date: The official publication date of accepted papers is the date<br=
>the proceedings are made available in the ACM Digital Library. This date m=
ay be<br>up to two weeks prior to the first day of the conference. The offi=
cial<br>publication date affects the deadline for any patent filings relate=
d to<br>published work.<br><br>Artefacts<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
<br>Authors are encouraged to make auxiliary material (artefacts like sourc=
e code,<br>test data, etc.) available with their paper. Authors can opt to =
have these<br>artefacts published alongside their paper in the ACM Digital =
Library (copyright<br>of artefacts remains with the authors). Artefacts mus=
t be included as part of<br>their submission to HotCRP and should consist o=
f a .zip file containing the<br>artefact materials, a README explaining the=
contents of the artefact and how it<br>should be used, and a LICENSE file.=
<br><br>If an accepted paper's artefacts are made permanently available=
for retrieval in<br>a publicly accessible archival repository like the ACM=
Digital Library, that<br>paper qualifies for an Artefact badge<br>(<a href=
=3D"https://www.acm.org/publications/policies/artifact-review-badging">http=
s://www.acm.org/publications/policies/artifact-review-badging</a>).<br><br>=
Program Committee<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br>Alexander Green =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 Standard Chartered, UK<br>David Thrane Christiansen =C2=A0 =C2=A0 =C2=
=A0 The Haskell Foundation, Denmark<br>Edsko de Vries =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Well-Typed LLP, Netherlands<br>Exe=
quiel Rivas =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0T=
allinn University of Technology<br>Facundo Dom=C3=ADnguez =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Tweag<br>Florian Zuleger =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 TU Vienna, Austria<br>Graham Hutton =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 University o=
f Nottingham, UK<br>Jasper Van der Jeugt =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0Snyk, Switzerland<br>Jennifer Paykin =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Intel, USA<br>Jesper Cockx =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Delft University of Technol=
ogy, Netherlands<br>Jose Nuno Oliveira =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0University of Minho & INESC TEC, Portugal<br>Michael Sperb=
er =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Active Group Gmb=
H, Germany<br>Michel Steuwer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0University of Edinburgh, UK<br>Niki Vazou (chair) =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IMDEA Software Institute, Spain<br=
>Rumyana Neykova =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Br=
unel University London, UK<br>Trevor L. McDonell (co-chair) =C2=A0 Utrecht =
University, Netherlands<br>Ugo Dal Lago =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0University of Bologna, Italy & INRIA,=
France<br>Wen Kokke =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 University of Edinburgh, UK<br>Leonidas Lampropoul=
os =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 University of Maryland, College Park,=
USA<br><br>If you have questions, please contact the chairs at <a href=3D"=
mailto:[email protected]">[email protected]</a> and<br><a href=3D"mai=
lto:[email protected]">[email protected]</a>.<br><br>=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
></font><br></div>
--00000000000024aecf05f7a2dd11--
--===============7438588878843049296==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KR2xhc2dvdy1o
YXNrZWxsLXVzZXJzIG1haWxpbmcgbGlzdApHbGFzZ293LWhhc2tlbGwtdXNlcnNAaGFza2VsbC5v
cmcKaHR0cDovL21haWwuaGFza2VsbC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL2dsYXNn
b3ctaGFza2VsbC11c2Vycwo=
--===============7438588878843049296==--