ICFP 2024: Call for Papers

--00000000000013e188060b5c89ae
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

             PACMPL Volume 7, Issue ICFP 2024

                           Call for Papers

       Accepted papers to be invited for presentation at

The 29th ACM SIGPLAN International Conference on Functional Programming

                              Milan, Italy

### Important dates

(All dates are in 2023 at 11.59pm Anywhere on Earth.)

Paper Submission -- Wed 28 Feb 2024  (AOE)
Paper Author Response -- Mon 29 Apr 12:00 - Wed 1 May 12:00 2024
Paper Notification --Mon 20 May 2024


### NEW THIS YEAR
-------------------

* Full double blind reviewing

### Scope
-------------------

PACMPL issue ICFP 2024 seeks original papers on the art and science of
functional programming. Submissions are invited on all topics from
principles to practice, from foundations to features, and from abstraction
to application. The scope includes all languages that encourage functional
programming, including both purely applicative and imperative languages, as
well as languages with objects, concurrency, or parallelism. Topics of
interest include (but are not limited to):

* Language Design: concurrency, parallelism, and distribution; modularity;
components and composition; meta-programming; macros; pattern matching;
type systems; type inference; dependent types; effect types; gradual types;
refinement types; session types; interoperability; domain-specific
languages; imperative programming; object-oriented programming; logic
programming; probabilistic programming; reactive programming; generic
programming; bidirectional programming.

* Implementation: abstract machines; virtual machines; interpretation;
compilation; compile-time and run-time optimisation; garbage collection and
memory management; runtime systems; multi-threading; exploiting parallel
hardware; interfaces to foreign functions, services, components, or
low-level machine resources.

* Software-Development Techniques: algorithms and data structures; design
patterns; specification; verification; validation; proof assistants;
debugging; testing; tracing; profiling; build systems; program synthesis.

* Foundations: formal semantics; lambda calculus; program equivalence;
rewriting; type theory; logic; category theory; computational effects;
continuations; control; state; names and binding; program verification.

* Analysis and Transformation: control flow; data flow; abstract
interpretation; partial evaluation; program calculation.

* Applications: symbolic computing; formal-methods tools; artificial
intelligence; systems programming; distributed systems and web programming;
hardware design; databases; scientific and numerical computing; graphical
user interfaces; graphics and multimedia; GPU programming; scripting;
system administration; security.

* Education: teaching introductory programming; mathematical proof; algebra=
.

Submissions will be evaluated according to their relevance, correctness,
significance, originality, and clarity. Each submission should explain its
contributions in both general and technical terms, clearly identifying what
has been accomplished, explaining why it is significant, and comparing it
with previous work. The technical content should be accessible to a broad
audience.

PACMPL issue ICFP 2024 also welcomes submissions in two separate categories
=E2=80=94 Functional Pearls and Experience Reports =E2=80=94 that must be m=
arked as such
when submitted and that need not report original research results. Detailed
guidelines on both categories are given at the end of this call.

In an effort to achieve a balanced, diverse program, each author may be
listed as a (co)author on a maximum of four submissions. Submissions from
underrepresented groups are encouraged. Authors who require financial
support to attend the conference can apply for PAC funding (
http://www.sigplan.org/PAC/).

The General Chair and PC Chair may not submit papers. PC members (other
than the PC Chair) may submit papers.

Please contact the Program Chair if you have questions or are concerned
about the appropriateness of a topic.

### Full Double-Blind Reviewing Process

ICFP 2024 will use a full double-blind reviewing process (similar to the
one used for POPL 2024 but different from the lightweight double-blind
process used in previous years). This means that identities of authors will
not be made visible to reviewers until after conditional-acceptance
decisions have been made, and then only for the conditionally-accepted
papers. The use of full double-blind reviewing has several consequences for
authors.

* Submissions: Authors must omit their names and institutions from their
paper submissions. In addition, references to authors=E2=80=99 own prior wo=
rk
should be in the third person (e.g., not =E2=80=9CWe build on our previous =
work =E2=80=A6=E2=80=9D
but rather =E2=80=9CWe build on the work of =E2=80=A6=E2=80=9D).

* Supplementary material: Authors are permitted to provide supplementary
material (e.g., detailed proofs, proof scripts, system implementations, or
experimental data) along with their submission, which reviewers may (but
are not required to) examine. This material may take the form of a single
file, such as a PDF or a tarball. Authors must fully anonymize any
supplementary material. Links to supplementary material on external
websites are not permitted.

* Author response: In responding to reviews, authors should not say
anything that reveals their identity, since author identities will not be
revealed to reviewers at that stage of the reviewing process.

* Dissemination of work under submission: Authors are welcome to
disseminate their ideas and post draft versions of their paper(s) on their
personal website, institutional repository, or arXiv (reviewers will be
asked to turn off arXiv notifications during the review period). But
authors should not take steps that would almost certainly reveal their
identities to members of the Program Committee, e.g., directly contacting
PC members or publicizing the work on widely-visible social media or major
mailing lists used by the community.

The purpose of the above restrictions is to help the Program Committee and
external reviewers come to a judgment about the paper without bias, not to
make it impossible for them to discover the authors=E2=80=99 identities if =
they
were to try. In particular, nothing should be done in the name of anonymity
that weakens the quality of the submission. However, there are occasionally
cases where adhering to the above restrictions is truly difficult or
impossible for one reason or another. In such cases, the authors should
contact the Program Chair to discuss the situation and how to handle it.


### Preparation of submissions
-------------------------------

* Deadline: The deadline for submissions is Wednesday, 28 February , 2024,
Anywhere on Earth (https://www.timeanddate.com/time/zones/aoe). This
deadline will be strictly enforced.

* Formatting: Submissions must be in PDF format, printable in black and
white on US Letter sized paper and interpretable by common PDF tools. All
submissions must adhere to the =E2=80=9CACM Small=E2=80=9D template that is=
 available (in
both LaTeX and Word formats) from
https://www.acm.org/publications/authors/submissions.

There is a limit of 25 pages for a full paper or Functional Pearl and 12
pages for an Experience Report; in either case, the bibliography and an
optional clearly marked appendix will not be counted against these limits.
Submissions that exceed the page limits or, for other reasons, do not meet
the requirements for formatting, will be summarily rejected.

See also PACMPL=E2=80=99s Information and Guidelines for Authors at
https://pacmpl.acm.org/authors.cfm.

* Submission: Submissions will be accepted at https://icfp24.hotcrp.com/

Improved versions of a paper may be submitted at any point before the
submission deadline using the same web interface.

* Author Response Period: Authors will have a 72-hour period, starting at
12:00 (noon) AOE on Monday, 29 April, 2024, to read reviews and respond to
them.

* Appendix and Supplementary Material: Authors have the option to include a
clearly marked appendix and/or to attach supplementary material to a
submission, on the understanding that reviewers may choose not to look at
such an appendix or supplementary material. Supplementary material may be
uploaded as a separate PDF document or tarball. Any supplementary material
must be uploaded at submission time, not by providing a URL in the paper
that points to an external repository. All supplementary material must be
anonymised.

* Authorship Policies: All submissions are expected to comply with the ACM
Policies for Authorship that are detailed at
https://www.acm.org/publications/authors/information-for-authors.

* Republication Policies: Each submission must adhere to SIGPLAN=E2=80=99s
republication policy, as explained on the web at
http://www.sigplan.org/Resources/Policies/Republication.

* ORCID: ORCID provides a persistent digital identifier (an ORCID iD) that
you own and control, and that distinguishes you from every other
researcher: https://orcid.org/. ACM now require an ORCID iD for every
author of a paper, not just the corresponding author. So, the author who is
filling out the permission form should make sure they have the ORCID iDs
for all of their coauthors before filling out the form. Any authors who do
not yet have an ORCID iD can go to https://orcid.org/register to have one
assigned.

### Review Process
-------------------
This section outlines the two-stage process with lightweight double-blind
reviewing that will be used to select papers for PACMPL issue ICFP 2024.
New this year, ICFP 2024 will adapt a full double-blind reviewing process.
More information see below.

ICFP 2024 will have an Associate Chair who will help the PC Chair monitor
reviews, solicit external expert reviews for submissions when there is not
enough expertise on the committee, and facilitate reviewer discussions.

PACMPL issue ICFP 2024 will employ a two-stage review process. The first
stage in the review process will assess submitted papers using the criteria
stated above and will allow for feedback and input on initial reviews
through the author response period mentioned previously. As a result of the
review process, a set of papers will be conditionally accepted and all
other papers will be rejected. Authors will be notified of these decisions
on 20 May, 2024.

Authors of conditionally accepted papers will be provided with committee
reviews along with a set of mandatory revisions. By 11 June, 2024, the
authors should provide a second revised submission. The second and final
reviewing phase assesses whether the mandatory revisions have been
adequately addressed by the authors and thereby determines the final
accept/reject status of the paper. The intent and expectation is that the
mandatory revisions can feasibly be addressed within three weeks.

The second submission should clearly identify how the mandatory revisions
were addressed. To that end, the second submission must be accompanied by a
cover letter mapping each mandatory revision request to specific parts of
the paper. The cover letter will facilitate a quick second review, allowing
for confirmation of final acceptance within two weeks. Conversely, the
absence of a cover letter will be grounds for the paper=E2=80=99s rejection=
.

### Information for Authors of Accepted Papers
----------------------------------------------
As a condition of acceptance, final versions of all papers must adhere to
the ACM Small format. The page limit for the final versions of papers will
be increased by two pages to help authors respond to reviewer comments and
mandatory revisions: 27 pages plus bibliography for a regular paper or
Functional Pearl, 14 pages plus bibliography for an Experience Report.

Authors of accepted submissions will be required to agree to one of the
three ACM licensing options, one of which is Creative Commons CC-BY
publication; this is the option recommended by the PACMPL editorial board.
A reasoned argument in favour of this option can be found in the article
Why CC-BY? published by OASPA, the Open Access Scholarly Publishers
Association. The other options are copyright transfer to ACM or retaining
copyright but granting ACM exclusive publication rights.

PACMPL is a Gold Open Access journal, and authors are encouraged to publish
their work under a CC-BY license. Gold Open Access guarantees permanent
free online access to the definitive version in the ACM Digital Library,
and the recommended CC-BY option also allows anyone to copy and distribute
the work with attribution. Gold Open Access has been made possible by
generous funding through ACM SIGPLAN, which will cover all open access
costs in the event authors cannot. Authors who can cover the costs may do
so by paying an Article Processing Charge (APC). PACMPL, SIGPLAN, and ACM
Headquarters are committed to exploring routes to making Gold Open Access
publication both affordable and sustainable.

ACM Author-Izer is a unique service that enables ACM authors to generate
and post links on either their home page or institutional repository for
visitors to download the definitive version of their articles from the ACM
Digital Library at no charge. Downloads through Author-Izer links are
captured in official ACM statistics, improving the accuracy of usage and
impact measurements. Consistently linking to the definitive version of an
ACM article should reduce user confusion over article versioning. After an
article has been published and assigned to the appropriate ACM Author
Profile pages, authors should visit
http://www.acm.org/publications/acm-author-izer-service to learn how to
create links for free downloads from the ACM DL.

The official publication date is the date the papers 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.

Authors of each accepted submission are invited to attend and be available
for the presentation of that paper at the conference. The schedule for
presentations will be determined and shared with authors after the full
program has been selected.

### Artifact Evaluation
-----------------------
Authors of papers that are conditionally accepted in the first phase of the
review process will be encouraged (but not required) to submit supporting
materials for Artifact Evaluation. These items will then be reviewed by an
Artifact Evaluation Committee, separate from the paper Review Committee,
whose task is to assess how the artifacts support the work described in the
associated paper. Papers that go through the Artifact Evaluation process
successfully will receive a seal of approval printed on the papers
themselves. Authors of accepted papers will be encouraged to make the
supporting materials publicly available upon publication of the papers, for
example, by including them as =E2=80=9Csource materials=E2=80=9D in the ACM=
 Digital
Library. An additional seal will mark papers whose artifacts are made
available, as outlined in the ACM guidelines for artifact badging.

Participation in Artifact Evaluation is voluntary and will not influence
the final decision regarding paper acceptance.

### Special categories of papers
-------------------------------
In addition to research papers, PACMPL issue ICFP solicits two kinds of
papers that do not require original research contributions: Functional
Pearls, which are full papers, and Experience Reports, which are limited to
half the length of a full paper. Authors submitting such papers should
consider the following guidelines.

* Functional Pearls
- A Functional Pearl is an elegant essay about something related to
functional programming. Examples include, but are not limited to:

- a new and thought-provoking way of looking at an old idea

- an instructive example of program calculation or proof

- a nifty presentation of an old or new data structure

- an interesting application of functional programming techniques

- a novel use or exposition of functional programming in the classroom

While pearls often demonstrate an idea through the development of a short
program, there is no requirement or expectation that they do so. Thus, they
encompass the notions of theoretical and educational pearls.

Functional Pearls are valued as highly and judged as rigorously as ordinary
papers, but using somewhat different criteria. In particular, a pearl is
not required to report original research, but, it should be concise,
instructive, and entertaining. A pearl is likely to be rejected if its
readers get bored, if the material gets too complicated, if too
much-specialised knowledge is needed, or if the writing is inelegant. The
key to writing a good pearl is polishing.

A submission that is intended to be treated as a pearl must be marked as
such on the submission web page and should contain the words =E2=80=9CFunct=
ional
Pearl=E2=80=9D somewhere in its title or subtitle. These steps will alert r=
eviewers
to use the appropriate evaluation criteria. Pearls will be combined with
ordinary papers, however, for the purpose of computing the conference=E2=80=
=99s
acceptance rate.

* Experience Reports
The purpose of an Experience Report is to describe the experience of using
functional programming in practice, whether in industrial application, tool
development, programming education, or any other area.

Possible topics for an Experience Report include, but are not limited to:

- insights gained from real-world projects using functional programming

- comparison of functional programming with conventional programming in the
context of an industrial project or a university curriculum

- project-management, business, or legal issues encountered when using
functional programming in a real-world project

- curricular issues encountered when using functional programming in
education

- real-world constraints that created special challenges for an
implementation of a functional language or for functional programming in
general

An Experience Report is distinguished from a normal PACMPL issue ICFP paper
by its title, by its length, and by the criteria used to evaluate it.

Both in the papers and in any citations, the title of each accepted
Experience Report must end with the words =E2=80=9C(Experience Report)=E2=
=80=9D in
parentheses. The acceptance rate for Experience Reports will be computed
and reported separately from the rate for ordinary papers.

Experience Report submissions can be at most 12 pages long, excluding
bibliography.

Each accepted Experience Report will be presented at the conference, but
depending on the number of Experience Reports and regular papers accepted,
authors of Experience Reports may be asked to give shorter talks.

Because the purpose of Experience Reports is to enable our community to
understand the application of functional programming, an acceptable
Experience Report need not add to the body of knowledge of the
functional-programming community by presenting novel results or
conclusions. It is sufficient if the report describes an illuminating
experience with functional programming, or provides evidence for a clear
thesis about the use of functional programming. The experience or thesis
must be relevant to ICFP, but it need not be novel.

The review committee will accept or reject Experience Reports based on
whether they judge the paper to illuminate some aspect of the use of
functional programming. Anecdotal evidence will be acceptable provided it
is well-argued and the author explains what efforts were made to gather as
much evidence as possible. Typically, papers that show how functional
programming was used are more convincing than papers that say only that
functional programming was used. It can be especially effective to present
comparisons of the situations before and after the experience described in
the paper, but other kinds of evidence would also make sense, depending on
context. Experience drawn from a single person=E2=80=99s experience may be
sufficient, but more weight will be given to evidence drawn from the
experience of groups of people.

An Experience Report should be short and to the point. For an industrial
project, it should make a claim about how well functional programming
worked and why; for a pedagogy paper, it might make a claim about the
suitability of a particular teaching style or educational exercise. Either
way, it should produce evidence to substantiate the claim. If functional
programming worked in this case in the same ways it has worked for others,
the paper need only summarise the results =E2=80=94 the main part of the pa=
per
should discuss how well it worked and in what context. Most readers will
not want to know all the details of the experience and its implementation,
but the paper should characterise it and its context well enough so that
readers can judge to what degree this experience is relevant to their own
circumstances. The paper should take care to highlight any unusual aspects;
specifics about the experience are more valuable than generalities about
functional programming.

If the paper not only describes experience but also presents new technical
results, or if the experience refutes cherished beliefs of the
functional-programming community, it may be better to submit it as a full
paper, which will be judged by the usual criteria of novelty, originality,
and relevance. The Program Chair will be happy to advise on any concerns
about which category to submit to.

### About PACMPL
----------------
Proceedings of the ACM on Programming Languages (PACMPL
https://pacmpl.acm.org/) is a Gold Open Access journal publishing research
on all aspects of programming languages, from design to implementation and
from mathematical formalisms to empirical studies. Each issue of the
journal is devoted to a particular subject area within programming
languages and will be announced through publicised Calls for Papers, like
this one.


### ICFP Organisers

General Chair:
  Marco Gaboardi (Boston University, USA)

Programme Chair:
  Brigitte Pientka (McGill University, Canada)

Associate Programme Chair:
  Gabriele Keller (Utrecht University, Netherlands)

Publicity Chair:
  Ilya Sergey (National University of Singapore, Singapore)

Programme Committee:

https://icfp24.sigplan.org/committee/icfp-2024-papers-icfp-papers-and-event=
s

-----------------------------------------------------------------------

--00000000000013e188060b5c89ae
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0PACMPL Vol=
ume 7, Issue ICFP 2024<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=A0Call for Papers<br><br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0Accepted papers to be invited for presentation a=
t<br>	 =C2=A0 <br>The 29th ACM SIGPLAN International Conference on Function=
al Programming<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0<di=
v>=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 Milan, Italy<br><br>### Important dates<br>=
<br>(All dates are in 2023 at 11.59pm Anywhere on Earth.)<br><br>Paper Subm=
ission -- Wed 28 Feb 2024 =C2=A0(AOE)<br>Paper Author Response -- Mon 29 Ap=
r 12:00 - Wed 1 May 12:00 2024<br>Paper Notification --Mon 20 May 2024<br><=
br><br>### NEW THIS YEAR<br>-------------------<br><br>* Full double blind =
reviewing<br><br>### Scope<br>-------------------<br><br>PACMPL issue ICFP =
2024 seeks original papers on the art and science of functional programming=
. Submissions are invited on all topics from principles to practice, from f=
oundations to features, and from abstraction to application. The scope incl=
udes all languages that encourage functional programming, including both pu=
rely applicative and imperative languages, as well as languages with object=
s, concurrency, or parallelism. Topics of interest include (but are not lim=
ited to):<br><br>* Language Design: concurrency, parallelism, and distribut=
ion; modularity; components and composition; meta-programming; macros; patt=
ern matching; type systems; type inference; dependent types; effect types; =
gradual types; refinement types; session types; interoperability; domain-sp=
ecific languages; imperative programming; object-oriented programming; logi=
c programming; probabilistic programming; reactive programming; generic pro=
gramming; bidirectional programming.<br><br>* Implementation: abstract mach=
ines; virtual machines; interpretation; compilation; compile-time and run-t=
ime optimisation; garbage collection and memory management; runtime systems=
; multi-threading; exploiting parallel hardware; interfaces to foreign func=
tions, services, components, or low-level machine resources.<br><br>* Softw=
are-Development Techniques: algorithms and data structures; design patterns=
; specification; verification; validation; proof assistants; debugging; tes=
ting; tracing; profiling; build systems; program synthesis.<br><br>* Founda=
tions: formal semantics; lambda calculus; program equivalence; rewriting; t=
ype theory; logic; category theory; computational effects; continuations; c=
ontrol; state; names and binding; program verification.<br><br>* Analysis a=
nd Transformation: control flow; data flow; abstract interpretation; partia=
l evaluation; program calculation.<br><br>* Applications: symbolic computin=
g; formal-methods tools; artificial intelligence; systems programming; dist=
ributed systems and web programming; hardware design; databases; scientific=
 and numerical computing; graphical user interfaces; graphics and multimedi=
a; GPU programming; scripting; system administration; security.<br><br>* Ed=
ucation: teaching introductory programming; mathematical proof; algebra.<br=
><br>Submissions will be evaluated according to their relevance, correctnes=
s, significance, originality, and clarity. Each submission should explain i=
ts contributions in both general and technical terms, clearly identifying w=
hat has been accomplished, explaining why it is significant, and comparing =
it with previous work. The technical content should be accessible to a broa=
d audience.<br><br>PACMPL issue ICFP 2024 also welcomes submissions in two =
separate categories =E2=80=94 Functional Pearls and Experience Reports =E2=
=80=94 that must be marked as such when submitted and that need not report =
original research results. Detailed guidelines on both categories are given=
 at the end of this call.<br><br>In an effort to achieve a balanced, divers=
e program, each author may be listed as a (co)author on a maximum of four s=
ubmissions. Submissions from underrepresented groups are encouraged. Author=
s who require financial support to attend the conference can apply for PAC =
funding (<a href=3D"http://www.sigplan.org/PAC/">http://www.sigplan.org/PAC=
/</a>).<br><br>The General Chair and PC Chair may not submit papers. PC mem=
bers (other than the PC Chair) may submit papers.<br><br>Please contact the=
 Program Chair if you have questions or are concerned about the appropriate=
ness of a topic.<br><br>### Full Double-Blind Reviewing Process <br><br>ICF=
P 2024 will use a full double-blind reviewing process (similar to the one u=
sed for POPL 2024 but different from the lightweight double-blind process u=
sed in previous years). This means that identities of authors will not be m=
ade visible to reviewers until after conditional-acceptance decisions have =
been made, and then only for the conditionally-accepted papers. The use of =
full double-blind reviewing has several consequences for authors.<br><br>* =
Submissions: Authors must omit their names and institutions from their pape=
r submissions. In addition, references to authors=E2=80=99 own prior work s=
hould be in the third person (e.g., not =E2=80=9CWe build on our previous w=
ork =E2=80=A6=E2=80=9D but rather =E2=80=9CWe build on the work of =E2=80=
=A6=E2=80=9D).<br><br>* Supplementary material: Authors are permitted to pr=
ovide supplementary material (e.g., detailed proofs, proof scripts, system =
implementations, or experimental data) along with their submission, which r=
eviewers may (but are not required to) examine. This material may take the =
form of a single file, such as a PDF or a tarball. Authors must fully anony=
mize any supplementary material. Links to supplementary material on externa=
l websites are not permitted.<br><br>* Author response: In responding to re=
views, authors should not say anything that reveals their identity, since a=
uthor identities will not be revealed to reviewers at that stage of the rev=
iewing process.<br><br>* Dissemination of work under submission: Authors ar=
e welcome to disseminate their ideas and post draft versions of their paper=
(s) on their personal website, institutional repository, or arXiv (reviewer=
s will be asked to turn off arXiv notifications during the review period). =
But authors should not take steps that would almost certainly reveal their =
identities to members of the Program Committee, e.g., directly contacting P=
C members or publicizing the work on widely-visible social media or major m=
ailing lists used by the community.<br><br>The purpose of the above restric=
tions is to help the Program Committee and external reviewers come to a jud=
gment about the paper without bias, not to make it impossible for them to d=
iscover the authors=E2=80=99 identities if they were to try. In particular,=
 nothing should be done in the name of anonymity that weakens the quality o=
f the submission. However, there are occasionally cases where adhering to t=
he above restrictions is truly difficult or impossible for one reason or an=
other. In such cases, the authors should contact the Program Chair to discu=
ss the situation and how to handle it.<br><br><br>### Preparation of submis=
sions<br>-------------------------------<br><br>* Deadline: The deadline fo=
r submissions is Wednesday, 28 February , 2024, Anywhere on Earth (<a href=
=3D"https://www.timeanddate.com/time/zones/aoe">https://www.timeanddate.com=
/time/zones/aoe</a>). This deadline will be strictly enforced.<br><br>* For=
matting: Submissions must be in PDF format, printable in black and white on=
 US Letter sized paper and interpretable by common PDF tools. All submissio=
ns must adhere to the =E2=80=9CACM Small=E2=80=9D template that is availabl=
e (in both LaTeX and Word formats) from <a href=3D"https://www.acm.org/publ=
ications/authors/submissions">https://www.acm.org/publications/authors/subm=
issions</a>.<br><br>There is a limit of 25 pages for a full paper or Functi=
onal Pearl and 12 pages for an Experience Report; in either case, the bibli=
ography and an optional clearly marked appendix will not be counted against=
 these limits. Submissions that exceed the page limits or, for other reason=
s, do not meet the requirements for formatting, will be summarily rejected.=
<br><br>See also PACMPL=E2=80=99s Information and Guidelines for Authors at=
 <a href=3D"https://pacmpl.acm.org/authors.cfm">https://pacmpl.acm.org/auth=
ors.cfm</a>.<br><br>* Submission: Submissions will be accepted at <a href=
=3D"https://icfp24.hotcrp.com/">https://icfp24.hotcrp.com/</a><br><br>Impro=
ved versions of a paper may be submitted at any point before the submission=
 deadline using the same web interface.<br><br>* Author Response Period: Au=
thors will have a 72-hour period, starting at 12:00 (noon) AOE on Monday, 2=
9 April, 2024, to read reviews and respond to them.<br><br>* Appendix and S=
upplementary Material: Authors have the option to include a clearly marked =
appendix and/or to attach supplementary material to a submission, on the un=
derstanding that reviewers may choose not to look at such an appendix or su=
pplementary material. Supplementary material may be uploaded as a separate =
PDF document or tarball. Any supplementary material must be uploaded at sub=
mission time, not by providing a URL in the paper that points to an externa=
l repository. All supplementary material must be anonymised.<br><br>* Autho=
rship Policies: All submissions are expected to comply with the ACM Policie=
s for Authorship that are detailed at <a href=3D"https://www.acm.org/public=
ations/authors/information-for-authors">https://www.acm.org/publications/au=
thors/information-for-authors</a>.<br><br>* Republication Policies: Each su=
bmission must adhere to SIGPLAN=E2=80=99s republication policy, as explaine=
d on the web at <a href=3D"http://www.sigplan.org/Resources/Policies/Republ=
ication">http://www.sigplan.org/Resources/Policies/Republication</a>.<br><b=
r>* ORCID: ORCID provides a persistent digital identifier (an ORCID iD) tha=
t you own and control, and that distinguishes you from every other research=
er: <a href=3D"https://orcid.org/">https://orcid.org/</a>. ACM now require =
an ORCID iD for every author of a paper, not just the corresponding author.=
 So, the author who is filling out the permission form should make sure the=
y have the ORCID iDs for all of their coauthors before filling out the form=
. Any authors who do not yet have an ORCID iD can go to <a href=3D"https://=
orcid.org/register">https://orcid.org/register</a> to have one assigned.<br=
><br>### Review Process<br>-------------------<br>This section outlines the=
 two-stage process with lightweight double-blind reviewing that will be use=
d to select papers for PACMPL issue ICFP 2024. New this year, ICFP 2024 wil=
l adapt a full double-blind reviewing process. More information see below.<=
br><br>ICFP 2024 will have an Associate Chair who will help the PC Chair mo=
nitor reviews, solicit external expert reviews for submissions when there i=
s not enough expertise on the committee, and facilitate reviewer discussion=
s.<br><br>PACMPL issue ICFP 2024 will employ a two-stage review process. Th=
e first stage in the review process will assess submitted papers using the =
criteria stated above and will allow for feedback and input on initial revi=
ews through the author response period mentioned previously. As a result of=
 the review process, a set of papers will be conditionally accepted and all=
 other papers will be rejected. Authors will be notified of these decisions=
 on 20 May, 2024.<br><br>Authors of conditionally accepted papers will be p=
rovided with committee reviews along with a set of mandatory revisions. By =
11 June, 2024, the authors should provide a second revised submission. The =
second and final reviewing phase assesses whether the mandatory revisions h=
ave been adequately addressed by the authors and thereby determines the fin=
al accept/reject status of the paper. The intent and expectation is that th=
e mandatory revisions can feasibly be addressed within three weeks.<br><br>=
The second submission should clearly identify how the mandatory revisions w=
ere addressed. To that end, the second submission must be accompanied by a =
cover letter mapping each mandatory revision request to specific parts of t=
he paper. The cover letter will facilitate a quick second review, allowing =
for confirmation of final acceptance within two weeks. Conversely, the abse=
nce of a cover letter will be grounds for the paper=E2=80=99s rejection.<br=
><br>### Information for Authors of Accepted Papers<br>--------------------=
--------------------------<br>As a condition of acceptance, final versions =
of all papers must adhere to the ACM Small format. The page limit for the f=
inal versions of papers will be increased by two pages to help authors resp=
ond to reviewer comments and mandatory revisions: 27 pages plus bibliograph=
y for a regular paper or Functional Pearl, 14 pages plus bibliography for a=
n Experience Report.<br><br>Authors of accepted submissions will be require=
d to agree to one of the three ACM licensing options, one of which is Creat=
ive Commons CC-BY publication; this is the option recommended by the PACMPL=
 editorial board. A reasoned argument in favour of this option can be found=
 in the article Why CC-BY? published by OASPA, the Open Access Scholarly Pu=
blishers Association. The other options are copyright transfer to ACM or re=
taining copyright but granting ACM exclusive publication rights.<br><br>PAC=
MPL is a Gold Open Access journal, and authors are encouraged to publish th=
eir work under a CC-BY license. Gold Open Access guarantees permanent free =
online access to the definitive version in the ACM Digital Library, and the=
 recommended CC-BY option also allows anyone to copy and distribute the wor=
k with attribution. Gold Open Access has been made possible by generous fun=
ding through ACM SIGPLAN, which will cover all open access costs in the eve=
nt authors cannot. Authors who can cover the costs may do so by paying an A=
rticle Processing Charge (APC). PACMPL, SIGPLAN, and ACM Headquarters are c=
ommitted to exploring routes to making Gold Open Access publication both af=
fordable and sustainable.<br><br>ACM Author-Izer is a unique service that e=
nables ACM authors to generate and post links on either their home page or =
institutional repository for visitors to download the definitive version of=
 their articles from the ACM Digital Library at no charge. Downloads throug=
h Author-Izer links are captured in official ACM statistics, improving the =
accuracy of usage and impact measurements. Consistently linking to the defi=
nitive version of an ACM article should reduce user confusion over article =
versioning. After an article has been published and assigned to the appropr=
iate ACM Author Profile pages, authors should visit <a href=3D"http://www.a=
cm.org/publications/acm-author-izer-service">http://www.acm.org/publication=
s/acm-author-izer-service</a> to learn how to create links for free downloa=
ds from the ACM DL.<br><br>The official publication date is the date the pa=
pers 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 publicatio=
n date affects the deadline for any patent filings related to published wor=
k.<br><br>Authors of each accepted submission are invited to attend and be =
available for the presentation of that paper at the conference. The schedul=
e for presentations will be determined and shared with authors after the fu=
ll program has been selected.<br><br>### Artifact Evaluation<br>-----------=
------------<br>Authors of papers that are conditionally accepted in the fi=
rst phase of the review process will be encouraged (but not required) to su=
bmit supporting materials for Artifact Evaluation. These items will then be=
 reviewed by an Artifact Evaluation Committee, separate from the paper Revi=
ew Committee, whose task is to assess how the artifacts support the work de=
scribed in the associated paper. Papers that go through the Artifact Evalua=
tion process successfully will receive a seal of approval printed on the pa=
pers themselves. Authors of accepted papers will be encouraged to make the =
supporting materials publicly available upon publication of the papers, for=
 example, by including them as =E2=80=9Csource materials=E2=80=9D in the AC=
M Digital Library. An additional seal will mark papers whose artifacts are =
made available, as outlined in the ACM guidelines for artifact badging.<br>=
<br>Participation in Artifact Evaluation is voluntary and will not influenc=
e the final decision regarding paper acceptance.<br><br>### Special categor=
ies of papers<br>-------------------------------<br>In addition to research=
 papers, PACMPL issue ICFP solicits two kinds of papers that do not require=
 original research contributions: Functional Pearls, which are full papers,=
 and Experience Reports, which are limited to half the length of a full pap=
er. Authors submitting such papers should consider the following guidelines=
.<br><br>* Functional Pearls<br>- A Functional Pearl is an elegant essay ab=
out something related to functional programming. Examples include, but are =
not limited to:<br><br>- a new and thought-provoking way of looking at an o=
ld idea<br><br>- an instructive example of program calculation or proof<br>=
<br>- a nifty presentation of an old or new data structure<br><br>- an inte=
resting application of functional programming techniques<br><br>- a novel u=
se or exposition of functional programming in the classroom<br><br>While pe=
arls often demonstrate an idea through the development of a short program, =
there is no requirement or expectation that they do so. Thus, they encompas=
s the notions of theoretical and educational pearls.<br><br>Functional Pear=
ls are valued as highly and judged as rigorously as ordinary papers, but us=
ing somewhat different criteria. In particular, a pearl is not required to =
report original research, but, it should be concise, instructive, and enter=
taining. A pearl is likely to be rejected if its readers get bored, if the =
material gets too complicated, if too much-specialised knowledge is needed,=
 or if the writing is inelegant. The key to writing a good pearl is polishi=
ng.<br><br>A submission that is intended to be treated as a pearl must be m=
arked as such on the submission web page and should contain the words =E2=
=80=9CFunctional Pearl=E2=80=9D somewhere in its title or subtitle. These s=
teps will alert reviewers to use the appropriate evaluation criteria. Pearl=
s will be combined with ordinary papers, however, for the purpose of comput=
ing the conference=E2=80=99s acceptance rate.<br><br>* Experience Reports<b=
r>The purpose of an Experience Report is to describe the experience of usin=
g functional programming in practice, whether in industrial application, to=
ol development, programming education, or any other area.<br><br>Possible t=
opics for an Experience Report include, but are not limited to:<br><br>- in=
sights gained from real-world projects using functional programming<br><br>=
- comparison of functional programming with conventional programming in the=
 context of an industrial project or a university curriculum<br><br>- proje=
ct-management, business, or legal issues encountered when using functional =
programming in a real-world project<br><br>- curricular issues encountered =
when using functional programming in education<br><br>- real-world constrai=
nts that created special challenges for an implementation of a functional l=
anguage or for functional programming in general<br><br>An Experience Repor=
t is distinguished from a normal PACMPL issue ICFP paper by its title, by i=
ts length, and by the criteria used to evaluate it.<br><br>Both in the pape=
rs and in any citations, the title of each accepted Experience Report must =
end with the words =E2=80=9C(Experience Report)=E2=80=9D in parentheses. Th=
e acceptance rate for Experience Reports will be computed and reported sepa=
rately from the rate for ordinary papers.<br><br>Experience Report submissi=
ons can be at most 12 pages long, excluding bibliography.<br><br>Each accep=
ted Experience Report will be presented at the conference, but depending on=
 the number of Experience Reports and regular papers accepted, authors of E=
xperience Reports may be asked to give shorter talks.<br><br>Because the pu=
rpose of Experience Reports is to enable our community to understand the ap=
plication of functional programming, an acceptable Experience Report need n=
ot add to the body of knowledge of the functional-programming community by =
presenting novel results or conclusions. It is sufficient if the report des=
cribes an illuminating experience with functional programming, or provides =
evidence for a clear thesis about the use of functional programming. The ex=
perience or thesis must be relevant to ICFP, but it need not be novel.<br><=
br>The review committee will accept or reject Experience Reports based on w=
hether they judge the paper to illuminate some aspect of the use of functio=
nal programming. Anecdotal evidence will be acceptable provided it is well-=
argued and the author explains what efforts were made to gather as much evi=
dence as possible. Typically, papers that show how functional programming w=
as used are more convincing than papers that say only that functional progr=
amming was used. It can be especially effective to present comparisons of t=
he situations before and after the experience described in the paper, but o=
ther kinds of evidence would also make sense, depending on context. Experie=
nce drawn from a single person=E2=80=99s experience may be sufficient, but =
more weight will be given to evidence drawn from the experience of groups o=
f people.<br><br>An Experience Report should be short and to the point. For=
 an industrial project, it should make a claim about how well functional pr=
ogramming worked and why; for a pedagogy paper, it might make a claim about=
 the suitability of a particular teaching style or educational exercise. Ei=
ther way, it should produce evidence to substantiate the claim. If function=
al programming worked in this case in the same ways it has worked for other=
s, the paper need only summarise the results =E2=80=94 the main part of the=
 paper should discuss how well it worked and in what context. Most readers =
will not want to know all the details of the experience and its implementat=
ion, but the paper should characterise it and its context well enough so th=
at readers can judge to what degree this experience is relevant to their ow=
n circumstances. The paper should take care to highlight any unusual aspect=
s; specifics about the experience are more valuable than generalities about=
 functional programming.<br><br>If the paper not only describes experience =
but also presents new technical results, or if the experience refutes cheri=
shed beliefs of the functional-programming community, it may be better to s=
ubmit it as a full paper, which will be judged by the usual criteria of nov=
elty, originality, and relevance. The Program Chair will be happy to advise=
 on any concerns about which category to submit to.<br><br>### About PACMPL=
<br>----------------<br>Proceedings of the ACM on Programming Languages (PA=
CMPL <a href=3D"https://pacmpl.acm.org/">https://pacmpl.acm.org/</a>) is a =
Gold Open Access journal publishing research on all aspects of programming =
languages, from design to implementation and from mathematical formalisms t=
o empirical studies. Each issue of the journal is devoted to a particular s=
ubject area within programming languages and will be announced through publ=
icised Calls for Papers, like this one.<br><br><br>### ICFP Organisers<br><=
br>General Chair:<br>=C2=A0 Marco Gaboardi (Boston University, USA)<br><br>=
Programme Chair:<br>=C2=A0 Brigitte Pientka (McGill University, Canada)<br>=
<br>Associate Programme Chair:<br>=C2=A0 Gabriele Keller (Utrecht Universit=
y, Netherlands)<br><br>Publicity Chair:<br>=C2=A0 Ilya Sergey (National Uni=
versity of Singapore, Singapore)<br><br>Programme Committee:<br>=C2=A0<a hr=
ef=3D"https://icfp24.sigplan.org/committee/icfp-2024-papers-icfp-papers-and=
-events">https://icfp24.sigplan.org/committee/icfp-2024-papers-icfp-papers-=
and-events</a><br><br>-----------------------------------------------------=
------------------<br></div></div>

--00000000000013e188060b5c89ae--