ICFP 2026: Call for Papers
ICFP Publicity <[email protected]> Tue, 11 Nov 2025 12:03:44 -0500
| Newsgroups | gmane.lisp.scheme.bigloo |
|---|---|
| Message-ID | <CAAmpXijiCM1HZZE3rCw=Guw7nCGfmoPp2yzwJdA3ieE61+9stg__12177.2093161539$1762880668$gmane$org@mail.gmail.com> |
--000000000000098168064354a26a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
ICFP 2026 Call for Papers
Accepted papers to be invited for presentation at:
*The 31st ACM SIGPLAN International Conference on Functional Programming*Au=
gust
23-29, 2026
Indianapolis, Indiana, USA
https://icfp26.sigplan.org
------------------------------
Submission Information
- *Submission web site*: https://icfp26.hotcrp.com
- *Submission Deadline*: 19 Feb 2026 (AoE)
Double-blind review
- Reviews: 20 Apr 2026 (AoE)
- Author Response: 20 Apr 2026 - 23 Apr 2026 (AoE)
- Notification of Conditional Acceptance: 14 May 2026 (AoE)
- Revision: 3 Jun 2026 (AoE)
- Final Notification: 10 Jun 2026 (AoE)
- Camera Ready: 1 Jul 2026 (AoE)
------------------------------
PACMPL issue ICFP 2026 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 typ=
es;
refinement types; session types; interoperability; domain-specific
languages; imperative programming; object-oriented programming; logic
programming; probabilistic programming; reactive programming; generic
programming; bidirectional programming; secure 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=
.
-
Analysis and Transformation: control flow; data flow; abstract
interpretation; partial evaluation; program calculation.
-
Foundations: formal semantics; lambda calculus; program equivalence;
rewriting; type theory; logic; category theory; computational effects;
continuations; control; state; names and binding; program verification.
-
Applications: symbolic computing; formal-methods tools; systems
programming; distributed systems and web programming; hardware design;
databases; scientific and numerical computing; graphical user interfaces=
;
graphics and multimedia; GPU programming; scripting; system administrati=
on;
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 2026 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. 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.
Double-blind Submissions
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#double-bind-submiss=
ions>
ICFP 2026 will use a full double-blind reviewing process. 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=
work
should be in the third person (e.g., not =E2=80=9CWe build on our previo=
us 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 must fully anonymize any supplementary
material (see below). Links to supplementary material on external websit=
es
are not permitted.
-
Author response: In responding to reviews, authors should not say
anything that reveals their identity, since author identities will not b=
e
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 the=
ir
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 contactin=
g
PC members or publicizing the work on widely-visible social media or maj=
or
mailing lists used by the community.
The purpose of the above restrictions is to help the Program Committee 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. The FAQ on
Double-Blind Reviewing (
https://popl24.sigplan.org/track/POPL-2024-popl-research-papers#FAQ-on-Doub=
le-Blind-Reviewing)
addresses many common scenarios and answers many common questions about
this topic. But there remain many grey areas and trade-offs. If you have
any doubts about how to interpret the double-blind rules or you encounter a
complex case that is not clearly covered by the FAQ, please contact the
Program Chair for guidance.
Preparation of submissions
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#preparation-of-subm=
issions>
The deadline for submissions is: *** Thursay, 19 Feb 2026 AoE *** (
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. Al=
l
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.
Please download the latest version of the ACM style from
https://www.acm.org/publications/authors/submissions, since the citation
format has recently been changed.
See also PACMPL=E2=80=99s Information and Guidelines for Authors at
https://pacmpl.acm.org/authors.cfm.
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 limit=
s.
Submissions that exceed the page limits or, for other reasons, do not me=
et
the requirements for formatting, will be desk rejected.
-
Submission: Submissions will be accepted at https://icfp26.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 96-hour period, starting at
00:00 (midnight) AoE on Monday, 20 April, 2026, to read reviews and resp=
ond
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 a=
t
such an appendix or supplementary material. Supplementary material may b=
e
uploaded as a separate PDF document or tarball. Any supplementary materi=
al
must be uploaded at submission time, not by providing a URL in the paper
that points to an external repository. All supplementary material must b=
e
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.
Review Process
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#review-process>
This section outlines the two-stage process with double-blind reviewing
that will be used to select papers for PACMPL issue ICFP 2026. Like last
year, ICFP 2026 will adapt a full double-blind reviewing process. More
information see below.
ICFP 2026 will have two Associate Chairs 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.
ICFP 2026 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 14 May, 2026.
Authors of conditionally accepted papers will be provided with committee
reviews along with a set of optional or mandatory revisions. By 3 June,
2026, the authors should provide a 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 a couple of 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 rejec=
tion.
Information for Authors of Accepted Papers
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#information-for-aut=
hors-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 journal is made available in
the ACM Digital Library. The journal issue and associated papers will be
published no earlier than 1 August, 2026. 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.
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.
By submitting your article to an ACM Publication, you are hereby
acknowledging that you and your co-authors are subject to all ACM
Publications Policies, including ACM=E2=80=99s new Publications Policy on R=
esearch
Involving Human Participants and Subjects. Alleged violations of this
policy or any ACM Publications Policy will be investigated by ACM and may
result in a full retraction of your paper, in addition to other potential
penalties, as per ACM Publications Policy.
Artifact Evaluation
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#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
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#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
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#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 for the purpose of computing the conference=E2=80=99s accep=
tance
rate.
Experience Reports
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#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
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#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.
Important update on ACM=E2=80=99s new open access publishing model for 2026=
ACM
Conferences:
<https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#important-update-on=
-acms-new-open-access-publishing-model-for-2026-acm-conferences>
Starting January 1, 2026, ACM will fully transition to Open Access. All ACM
publications, including those from ACM-sponsored conferences, will be 100%
Open Access. Authors will have two primary options for publishing Open
Access articles with ACM: the ACM Open institutional model or by paying
Article Processing Charges (APCs). With over 1,800 institutions already
part of ACM Open, the majority of ACM-sponsored conference papers will not
require APCs from authors or conferences (currently, around 70=E2=80=9375%)=
.
Authors from institutions not participating in ACM Open will need to pay an
APC to publish their papers, unless they qualify for a geographic or
discretionary waiver. To find out whether an APC applies to your article,
please consult the list of participating institutions
<https://libraries.acm.org/acmopen/open-participants> in ACM Open and
review the APC Waivers and Discounts Policy
<https://www.acm.org/publications/policies/policy-on-open-access-apc-waiver=
s-and-discounts>
.
To support a smooth transition and encourage broader ACM Open
participation, ACM has introduced a temporary subsidy on APC pricing for
2026, funded directly by ACM. This pricing applies to all articles
published in ACM and SIG sponsored conferences taking place in 2026. The
subsidized conference pricing for 2026 is as follows:
Authors No ACM or SIG members At least 1 ACM or SIG member
ACM and SIG Sponsored Conference Article $350 $250
From a lower-middle-income country
<https://www.acm.org/publications/policies/lower-middle-income-countries>
$175 $125
This represents a 65% discount <https://www.acm.org/publications/openaccess=
>,
funded directly by ACM. Authors are encouraged to help advocate for their
institutions to join ACM Open during this transition period.
--000000000000098168064354a26a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><h2 style=3D"box-sizing:border-box;font-family:"Helve=
tica Neue",Helvetica,Arial,sans-serif;font-weight:500;line-height:1.1;=
color:rgb(51,51,51);margin-top:20px;margin-bottom:10px;font-size:30px">ICFP=
2026 Call for Papers</h2><div><p style=3D"box-sizing:border-box;margin:0px=
0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvet=
ica,Arial,sans-serif;font-size:14px">Accepted papers to be invited for pres=
entation at:</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color=
:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-=
serif;font-size:14px"><b>The <i>31st ACM SIGPLAN International Conference o=
n Functional Programming<br></i></b>August 23-29, 2026<br>Indianapolis, Ind=
iana, USA<br><a href=3D"https://icfp26.sigplan.org/">https://icfp26.sigplan=
.org</a>=C2=A0</p><hr style=3D"box-sizing:content-box;height:0px;margin-top=
:20px;margin-bottom:20px;border-right:0px;border-bottom:0px;border-left:0px=
;border-top-style:solid;border-top-color:rgb(238,238,238);font-family:"=
;Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-fami=
ly:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">Su=
bmission Information</p><ul style=3D"box-sizing:border-box;margin-top:0px;m=
argin-bottom:10px;color:rgb(51,51,51);font-family:"Helvetica Neue"=
;,Helvetica,Arial,sans-serif;font-size:14px"><li style=3D"box-sizing:border=
-box"><b>Submission web site</b>:=C2=A0<a href=3D"https://icfp26.hotcrp.com=
/" style=3D"background-color:transparent;box-sizing:border-box;color:rgb(51=
,122,183);text-decoration-line:none;word-break:break-word">https://icfp26.h=
otcrp.com</a></li><li style=3D"box-sizing:border-box"><b>Submission Deadlin=
e</b>: 19 Feb 2026 (AoE)</li></ul></div><p style=3D"box-sizing:border-box;m=
argin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue&quo=
t;,Helvetica,Arial,sans-serif;font-size:14px">Double-blind review</p><ul st=
yle=3D"box-sizing:border-box;margin-top:0px;margin-bottom:10px;color:rgb(51=
,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;f=
ont-size:14px"><li style=3D"box-sizing:border-box">Reviews: 20 Apr 2026 (Ao=
E)</li><li style=3D"box-sizing:border-box">Author Response: 20 Apr 2026 - 2=
3 Apr 2026 (AoE)</li><li style=3D"box-sizing:border-box">Notification of Co=
nditional Acceptance: 14 May 2026 (AoE)</li><li style=3D"box-sizing:border-=
box">Revision: 3 Jun 2026 (AoE)</li><li style=3D"box-sizing:border-box">Fin=
al Notification: 10 Jun 2026 (AoE)</li><li style=3D"box-sizing:border-box">=
Camera Ready: 1 Jul 2026 (AoE)</li></ul><hr style=3D"box-sizing:content-box=
;height:0px;margin-top:20px;margin-bottom:20px;border-right:0px;border-bott=
om:0px;border-left:0px;border-top-style:solid;border-top-color:rgb(238,238,=
238);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font=
-size:14px"><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb=
(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-seri=
f;font-size:14px">PACMPL issue ICFP 2026 seeks original papers on the art a=
nd science of functional programming. Submissions are invited on all topics=
from principles to practice, from foundations to features, and from abstra=
ction to application. The scope includes all languages that encourage funct=
ional programming, including both purely applicative and imperative languag=
es, as well as languages with objects, concurrency, or parallelism. Topics =
of interest include (but are not limited to):</p><ul style=3D"box-sizing:bo=
rder-box;margin-top:0px;margin-bottom:10px;color:rgb(51,51,51);font-family:=
"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><li s=
tyle=3D"box-sizing:border-box"><p style=3D"box-sizing:border-box;margin:0px=
0px 10px">Language Design: concurrency, parallelism, and distribution; mod=
ularity; components and composition; meta-programming; macros; pattern matc=
hing; type systems; type inference; dependent types; effect types; gradual =
types; refinement types; session types; interoperability; domain-specific l=
anguages; imperative programming; object-oriented programming; logic progra=
mming; probabilistic programming; reactive programming; generic programming=
; bidirectional programming; secure programming.</p></li><li style=3D"box-s=
izing:border-box"><p style=3D"box-sizing:border-box;margin:0px 0px 10px">Im=
plementation: abstract machines; virtual machines; interpretation; compilat=
ion; 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 machin=
e resources.</p></li><li style=3D"box-sizing:border-box"><p style=3D"box-si=
zing:border-box;margin:0px 0px 10px">Software-Development Techniques: algor=
ithms and data structures; design patterns; specification; verification; va=
lidation; proof assistants; debugging; testing; tracing; profiling; build s=
ystems; program synthesis.</p></li><li style=3D"box-sizing:border-box"><p s=
tyle=3D"box-sizing:border-box;margin:0px 0px 10px">Analysis and Transformat=
ion: control flow; data flow; abstract interpretation; partial evaluation; =
program calculation.</p></li><li style=3D"box-sizing:border-box"><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px">Foundations: formal semantic=
s; lambda calculus; program equivalence; rewriting; type theory; logic; cat=
egory theory; computational effects; continuations; control; state; names a=
nd binding; program verification.</p></li><li style=3D"box-sizing:border-bo=
x"><p style=3D"box-sizing:border-box;margin:0px 0px 10px">Applications: sym=
bolic computing; formal-methods tools; systems programming; distributed sys=
tems and web programming; hardware design; databases; scientific and numeri=
cal computing; graphical user interfaces; graphics and multimedia; GPU prog=
ramming; scripting; system administration; security.</p></li><li style=3D"b=
ox-sizing:border-box"><p style=3D"box-sizing:border-box;margin:0px 0px 10px=
">Education: teaching introductory programming; mathematical proof; algebra=
.</p></li></ul><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:=
rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-s=
erif;font-size:14px">Submissions will be evaluated according to their relev=
ance, correctness, significance, originality, and clarity. Each submission =
should explain its contributions in both general and technical terms, clear=
ly identifying what has been accomplished, explaining why it is significant=
, and comparing it with previous work. The technical content should be acce=
ssible to a broad audience.</p><p style=3D"box-sizing:border-box;margin:0px=
0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvet=
ica,Arial,sans-serif;font-size:14px">PACMPL issue ICFP 2026 also welcomes s=
ubmissions in two separate categories =E2=80=94 Functional Pearls and Exper=
ience Reports =E2=80=94 that must be marked as such when submitted and that=
=C2=A0<em style=3D"box-sizing:border-box">need not</em>=C2=A0report origina=
l research results. Detailed guidelines on both categories are given at the=
end of this call.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px=
;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial=
,sans-serif;font-size:14px">In an effort to achieve a balanced, diverse pro=
gram, each author may be listed as a (co)author on a maximum of four submis=
sions. Authors who require financial support to attend the conference can a=
pply for PAC funding (<a href=3D"http://www.sigplan.org/PAC/" style=3D"box-=
sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-d=
ecoration-line:none;word-break:break-word">http://www.sigplan.org/PAC/</a>)=
.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,=
51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-=
size:14px">The General Chair and PC Chair may not submit papers. PC members=
(other than the PC Chair) may submit papers.</p><p style=3D"box-sizing:bor=
der-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica=
Neue",Helvetica,Arial,sans-serif;font-size:14px">Please contact the P=
rogram Chair if you have questions or are concerned about the appropriatene=
ss of a topic.</p><h2 style=3D"box-sizing:border-box;font-family:"Helv=
etica Neue",Helvetica,Arial,sans-serif;font-weight:500;line-height:1.1=
;color:rgb(51,51,51);margin-top:20px;margin-bottom:10px;font-size:30px"><a =
href=3D"https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#double-bind-=
submissions" id=3D"gmail-double-bind-submissions" class=3D"gmail-anchor-lin=
k" style=3D"box-sizing:border-box;background-color:transparent;color:inheri=
t;text-decoration:inherit;word-break:break-word">Double-blind Submissions</=
a></h2><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,5=
1,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;fon=
t-size:14px">ICFP 2026 will use a full double-blind reviewing process. This=
means that identities of authors will not be made visible to reviewers unt=
il 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.</p><ul style=3D"box-sizing:border-box=
;margin-top:0px;margin-bottom:10px;color:rgb(51,51,51);font-family:"He=
lvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><li style=3D"=
box-sizing:border-box"><p style=3D"box-sizing:border-box;margin:0px 0px 10p=
x">Submissions: Authors must omit their names and institutions from their p=
aper submissions. In addition, references to authors=E2=80=99 own prior wor=
k should be in the third person (e.g., not =E2=80=9CWe build on our previou=
s work =E2=80=A6=E2=80=9D but rather =E2=80=9CWe build on the work of =E2=
=80=A6=E2=80=9D).</p></li><li style=3D"box-sizing:border-box"><p style=3D"b=
ox-sizing:border-box;margin:0px 0px 10px">Supplementary material: Authors m=
ust fully anonymize any supplementary material (see below). Links to supple=
mentary material on external websites are not permitted.</p></li><li style=
=3D"box-sizing:border-box"><p style=3D"box-sizing:border-box;margin:0px 0px=
10px">Author response: In responding to reviews, authors should not say an=
ything that reveals their identity, since author identities will not be rev=
ealed to reviewers at that stage of the reviewing process.</p></li><li styl=
e=3D"box-sizing:border-box"><p style=3D"box-sizing:border-box;margin:0px 0p=
x 10px">Dissemination of work under submission: Authors are welcome to diss=
eminate their ideas and post draft versions of their paper(s) on their pers=
onal website, institutional repository, or arXiv (reviewers will be asked t=
o turn off arXiv notifications during the review period). But authors shoul=
d not take steps that would almost certainly reveal their identities to mem=
bers of the Program Committee, e.g., directly contacting PC members or publ=
icizing the work on widely-visible social media or major mailing lists used=
by the community.</p></li></ul><p style=3D"box-sizing:border-box;margin:0p=
x 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helve=
tica,Arial,sans-serif;font-size:14px">The purpose of the above restrictions=
is to help the Program Committee come to a judgment about the paper withou=
t 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 t=
he name of anonymity that weakens the quality of the submission. However, t=
here are occasionally cases where adhering to the above restrictions is tru=
ly difficult or impossible for one reason or another. In such cases, the au=
thors should contact the Program Chair to discuss the situation and how to =
handle it. The FAQ on Double-Blind Reviewing (<a href=3D"https://popl24.sig=
plan.org/track/POPL-2024-popl-research-papers#FAQ-on-Double-Blind-Reviewing=
" style=3D"box-sizing:border-box;background-color:transparent;color:rgb(51,=
122,183);text-decoration-line:none;word-break:break-word">https://popl24.si=
gplan.org/track/POPL-2024-popl-research-papers#FAQ-on-Double-Blind-Reviewin=
g</a>) addresses many common scenarios and answers many common questions ab=
out this topic. But there remain many grey areas and trade-offs. If you hav=
e any doubts about how to interpret the double-blind rules or you encounter=
a complex case that is not clearly covered by the FAQ, please contact the =
Program Chair for guidance.</p><h2 style=3D"box-sizing:border-box;font-fami=
ly:"Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:500;li=
ne-height:1.1;color:rgb(51,51,51);margin-top:20px;margin-bottom:10px;font-s=
ize:30px"><a href=3D"https://icfp26.sigplan.org/track/icfp-2026-icfp-papers=
#preparation-of-submissions" id=3D"gmail-preparation-of-submissions" class=
=3D"gmail-anchor-link" style=3D"box-sizing:border-box;background-color:tran=
sparent;color:inherit;text-decoration:inherit;word-break:break-word">Prepar=
ation of submissions</a></h2><p style=3D"box-sizing:border-box;margin:0px 0=
px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetic=
a,Arial,sans-serif;font-size:14px">The deadline for submissions is: <b>** T=
hursay, 19 Feb 2026 AoE **</b> (<a href=3D"https://www.timeanddate.com/time=
/zones/aoe" style=3D"box-sizing:border-box;background-color:transparent;col=
or:rgb(51,122,183);text-decoration-line:none;word-break:break-word">https:/=
/www.timeanddate.com/time/zones/aoe</a>). This deadline will be strictly en=
forced.</p><ul style=3D"box-sizing:border-box;margin-top:0px;margin-bottom:=
10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,A=
rial,sans-serif;font-size:14px"><li style=3D"box-sizing:border-box"><p styl=
e=3D"box-sizing:border-box;margin:0px 0px 10px">Formatting: Submissions mus=
t be in PDF format, printable in black and white on US Letter sized paper a=
nd 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 W=
ord formats) from=C2=A0<a href=3D"https://www.acm.org/publications/authors/=
submissions" style=3D"box-sizing:border-box;background-color:transparent;co=
lor:rgb(51,122,183);text-decoration-line:none;word-break:break-word">https:=
//www.acm.org/publications/authors/submissions</a>.</p><p style=3D"box-sizi=
ng:border-box;margin:0px 0px 10px">Please download the latest version of th=
e ACM style from=C2=A0<a href=3D"https://www.acm.org/publications/authors/s=
ubmissions" style=3D"box-sizing:border-box;background-color:transparent;col=
or:rgb(51,122,183);text-decoration-line:none;word-break:break-word">https:/=
/www.acm.org/publications/authors/submissions</a>, since the citation forma=
t has recently been changed.</p><p style=3D"box-sizing:border-box;margin:0p=
x 0px 10px">See also PACMPL=E2=80=99s Information and Guidelines for Author=
s at=C2=A0<a href=3D"https://pacmpl.acm.org/authors.cfm" style=3D"box-sizin=
g:border-box;background-color:transparent;color:rgb(51,122,183);text-decora=
tion-line:none;word-break:break-word">https://pacmpl.acm.org/authors.cfm</a=
>.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px">There is a lim=
it of=C2=A0<em style=3D"box-sizing:border-box">25 pages</em>=C2=A0for a ful=
l paper or Functional Pearl and=C2=A0<em style=3D"box-sizing:border-box">12=
pages</em>=C2=A0for 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 n=
ot meet the requirements for formatting, will be desk rejected.</p></li><li=
style=3D"box-sizing:border-box"><p style=3D"box-sizing:border-box;margin:0=
px 0px 10px">Submission: Submissions will be accepted at=C2=A0<a href=3D"ht=
tps://icfp26.hotcrp.com/" style=3D"box-sizing:border-box;background-color:t=
ransparent;color:rgb(51,122,183);text-decoration-line:none;word-break:break=
-word">https://icfp26.hotcrp.com</a></p><p style=3D"box-sizing:border-box;m=
argin:0px 0px 10px">Improved versions of a paper may be submitted at any po=
int before the submission deadline using the same web interface.</p></li><l=
i style=3D"box-sizing:border-box"><p style=3D"box-sizing:border-box;margin:=
0px 0px 10px">Author Response Period: Authors will have a 96-hour period, s=
tarting at 00:00 (midnight) AoE on Monday, 20 April, 2026, to read reviews =
and respond to them.</p></li><li style=3D"box-sizing:border-box"><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px">Appendix and Supplementary M=
aterial: Authors have the option to include a clearly marked appendix and/o=
r to attach supplementary material to a submission, on the understanding th=
at reviewers may choose not to look at such an appendix or supplementary ma=
terial. Supplementary material may be uploaded as a separate PDF document o=
r 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.</p></li><li style=3D"box-siz=
ing:border-box"><p style=3D"box-sizing:border-box;margin:0px 0px 10px">Auth=
orship Policies: All submissions are expected to comply with the ACM Polici=
es for Authorship that are detailed at=C2=A0<a href=3D"https://www.acm.org/=
publications/authors/information-for-authors" style=3D"box-sizing:border-bo=
x;background-color:transparent;color:rgb(51,122,183);text-decoration-line:n=
one;word-break:break-word">https://www.acm.org/publications/authors/informa=
tion-for-authors</a>.</p></li><li style=3D"box-sizing:border-box"><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px">Republication Policies: Each=
submission must adhere to SIGPLAN=E2=80=99s republication policy, as expla=
ined on the web at=C2=A0<a href=3D"http://www.sigplan.org/Resources/Policie=
s/Republication" style=3D"box-sizing:border-box;background-color:transparen=
t;color:rgb(51,122,183);text-decoration-line:none;word-break:break-word">ht=
tp://www.sigplan.org/Resources/Policies/Republication</a>.</p></li></ul><h2=
style=3D"box-sizing:border-box;font-family:"Helvetica Neue",Helv=
etica,Arial,sans-serif;font-weight:500;line-height:1.1;color:rgb(51,51,51);=
margin-top:20px;margin-bottom:10px;font-size:30px"><a href=3D"https://icfp2=
6.sigplan.org/track/icfp-2026-icfp-papers#review-process" id=3D"gmail-revie=
w-process" class=3D"gmail-anchor-link" style=3D"box-sizing:border-box;backg=
round-color:transparent;color:inherit;text-decoration:inherit;word-break:br=
eak-word">Review Process</a></h2><p style=3D"box-sizing:border-box;margin:0=
px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helv=
etica,Arial,sans-serif;font-size:14px">This section outlines the two-stage =
process with double-blind reviewing that will be used to select papers for =
PACMPL issue ICFP 2026. Like last year, ICFP 2026 will adapt a full double-=
blind reviewing process. More information see below.</p><p style=3D"box-siz=
ing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"He=
lvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">ICFP 2026 wil=
l have two Associate Chairs who will help the PC Chair monitor reviews, sol=
icit external expert reviews for submissions when there is not enough exper=
tise on the committee, and facilitate reviewer discussions.</p><p style=3D"=
box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:&=
quot;Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">ICFP 2=
026 will employ a two-stage review process. The first stage in the review p=
rocess will assess submitted papers using the criteria stated above and wil=
l allow for feedback and input on initial reviews through the author respon=
se period mentioned previously. As a result of the review process, a set of=
papers will be conditionally accepted and all other papers will be rejecte=
d. Authors will be notified of these decisions on 14 May, 2026.</p><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-fami=
ly:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">Au=
thors of conditionally accepted papers will be provided with committee revi=
ews along with a set of optional or mandatory revisions. By 3 June, 2026, t=
he authors should provide a revised submission. The second and final review=
ing phase assesses whether the mandatory revisions have been adequately add=
ressed by the authors and thereby determines the final accept/reject status=
of the paper. The intent and expectation is that the mandatory revisions c=
an feasibly be addressed within a couple of weeks.</p><p style=3D"box-sizin=
g:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helv=
etica Neue",Helvetica,Arial,sans-serif;font-size:14px">The second subm=
ission should clearly identify how the mandatory revisions were addressed. =
To that end, the second submission=C2=A0<em style=3D"box-sizing:border-box"=
>must be accompanied by a cover letter</em>=C2=A0mapping each mandatory rev=
ision request to specific parts of the paper. The cover letter will facilit=
ate a quick second review, allowing for confirmation of final acceptance wi=
thin two weeks. Conversely, the absence of a cover letter will be grounds f=
or the paper=E2=80=99s rejection.</p><h2 style=3D"box-sizing:border-box;fon=
t-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:=
500;line-height:1.1;color:rgb(51,51,51);margin-top:20px;margin-bottom:10px;=
font-size:30px"><a href=3D"https://icfp26.sigplan.org/track/icfp-2026-icfp-=
papers#information-for-authors-of-accepted-papers" id=3D"gmail-information-=
for-authors-of-accepted-papers" class=3D"gmail-anchor-link" style=3D"box-si=
zing:border-box;background-color:transparent;color:inherit;text-decoration:=
inherit;word-break:break-word">Information for Authors of Accepted Papers</=
a></h2><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,5=
1,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;fon=
t-size:14px">As a condition of acceptance, final versions of all papers mus=
t adhere to the ACM Small format. The page limit for the final versions of =
papers will be=C2=A0<em style=3D"box-sizing:border-box">increased by two pa=
ges</em>=C2=A0to help authors respond to reviewer comments and mandatory re=
visions: 27 pages plus bibliography for a regular paper or Functional Pearl=
, 14 pages plus bibliography for an Experience Report.</p><p style=3D"box-s=
izing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"=
Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">Authors of =
accepted submissions will be required to agree to one of the three ACM lice=
nsing options, one of which is Creative Commons CC-BY publication; this is =
the option recommended by the PACMPL editorial board. A reasoned argument i=
n 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 excl=
usive publication rights.</p><p style=3D"box-sizing:border-box;margin:0px 0=
px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetic=
a,Arial,sans-serif;font-size:14px">PACMPL is a Gold Open Access journal, an=
d authors are encouraged to publish their work under a CC-BY license. Gold =
Open Access guarantees permanent free online access to the definitive versi=
on 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 co=
ver the costs may do so by paying an Article Processing Charge (APC). PACMP=
L, SIGPLAN, and ACM Headquarters are committed to exploring routes to makin=
g Gold Open Access publication both affordable and sustainable.</p><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-fami=
ly:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">AC=
M Author-Izer is a unique service that enables ACM authors to generate and =
post links on either their home page or institutional repository for visito=
rs to download the definitive version of their articles from the ACM Digita=
l Library at no charge. Downloads through Author-Izer links are captured in=
official ACM statistics, improving the accuracy of usage and impact measur=
ements. Consistently linking to the definitive version of an ACM article sh=
ould reduce user confusion over article versioning. After an article has be=
en published and assigned to the appropriate ACM Author Profile pages, auth=
ors should visit=C2=A0<a href=3D"http://www.acm.org/publications/acm-author=
-izer-service" style=3D"box-sizing:border-box;background-color:transparent;=
color:rgb(51,122,183);text-decoration-line:none;word-break:break-word">http=
://www.acm.org/publications/acm-author-izer-service</a>=C2=A0to learn how t=
o create links for free downloads from the ACM DL.</p><p style=3D"box-sizin=
g:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helv=
etica Neue",Helvetica,Arial,sans-serif;font-size:14px">The official pu=
blication date is the date the journal is made available in the ACM Digital=
Library. The journal issue and associated papers will be published no earl=
ier than 1 August, 2026. The official publication date affects the deadline=
for any patent filings related to published work.</p><p style=3D"box-sizin=
g:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helv=
etica Neue",Helvetica,Arial,sans-serif;font-size:14px">Authors of each=
accepted submission are invited to attend and be available for the present=
ation of that paper at the conference. The schedule for presentations will =
be determined and shared with authors after the full program has been selec=
ted.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,=
51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;fo=
nt-size:14px">ORCID: ORCID provides a persistent digital identifier (an ORC=
ID iD) that you own and control, and that distinguishes you from every othe=
r researcher:=C2=A0<a href=3D"https://orcid.org/" style=3D"box-sizing:borde=
r-box;background-color:transparent;color:rgb(51,122,183);text-decoration-li=
ne:none;word-break:break-word">https://orcid.org/</a>. ACM now require an O=
RCID 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 ha=
ve the ORCID iDs for all of their coauthors before filling out the form. An=
y authors who do not yet have an ORCID iD can go to=C2=A0<a href=3D"https:/=
/orcid.org/register" style=3D"box-sizing:border-box;background-color:transp=
arent;color:rgb(51,122,183);text-decoration-line:none;word-break:break-word=
">https://orcid.org/register</a>=C2=A0to have one assigned.</p><p style=3D"=
box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:&=
quot;Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">By sub=
mitting your article to an ACM Publication, you are hereby acknowledging th=
at you and your co-authors are subject to all ACM Publications Policies, in=
cluding ACM=E2=80=99s new Publications Policy on Research Involving Human P=
articipants and Subjects. Alleged violations of this policy or any ACM Publ=
ications Policy will be investigated by ACM and may result in a full retrac=
tion of your paper, in addition to other potential penalties, as per ACM Pu=
blications Policy.</p><h2 style=3D"box-sizing:border-box;font-family:"=
Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:500;line-height=
:1.1;color:rgb(51,51,51);margin-top:20px;margin-bottom:10px;font-size:30px"=
><a href=3D"https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#artifact=
-evaluation" id=3D"gmail-artifact-evaluation" class=3D"gmail-anchor-link" s=
tyle=3D"box-sizing:border-box;background-color:transparent;color:inherit;te=
xt-decoration:inherit;word-break:break-word">Artifact Evaluation</a></h2><p=
style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);fon=
t-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14=
px">Authors of papers that are conditionally accepted in the first phase of=
the review process will be encouraged (but not required) to submit support=
ing 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 t=
he associated paper. Papers that go through the Artifact Evaluation process=
successfully will receive a seal of approval printed on the papers themsel=
ves. Authors of accepted papers will be encouraged to make the supporting m=
aterials publicly available upon publication of the papers, for example, by=
including them as =E2=80=9Csource materials=E2=80=9D in the ACM Digital Li=
brary. An additional seal will mark papers whose artifacts are made availab=
le, as outlined in the ACM guidelines for artifact badging.</p><p style=3D"=
box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:&=
quot;Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">Partic=
ipation in Artifact Evaluation is voluntary and=C2=A0<em style=3D"box-sizin=
g:border-box">will not influence</em>=C2=A0the final decision regarding pap=
er acceptance.</p><h2 style=3D"box-sizing:border-box;font-family:"Helv=
etica Neue",Helvetica,Arial,sans-serif;font-weight:500;line-height:1.1=
;color:rgb(51,51,51);margin-top:20px;margin-bottom:10px;font-size:30px"><a =
href=3D"https://icfp26.sigplan.org/track/icfp-2026-icfp-papers#special-cate=
gories-of-papers" id=3D"gmail-special-categories-of-papers" class=3D"gmail-=
anchor-link" style=3D"box-sizing:border-box;background-color:transparent;co=
lor:inherit;text-decoration:inherit;word-break:break-word">Special categori=
es of papers</a></h2><p style=3D"box-sizing:border-box;margin:0px 0px 10px;=
color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,=
sans-serif;font-size:14px">In addition to research papers, PACMPL issue ICF=
P solicits two kinds of papers that do not require original research contri=
butions: Functional Pearls, which are full papers, and Experience Reports, =
which are limited to half the length of a full paper. Authors submitting su=
ch papers should consider the following guidelines.</p><h4 style=3D"box-siz=
ing:border-box;font-family:"Helvetica Neue",Helvetica,Arial,sans-=
serif;font-weight:500;line-height:1.1;color:rgb(51,51,51);margin-top:10px;m=
argin-bottom:10px;font-size:18px"><a href=3D"https://icfp26.sigplan.org/tra=
ck/icfp-2026-icfp-papers#functional-pearls" id=3D"gmail-functional-pearls" =
class=3D"gmail-anchor-link" style=3D"box-sizing:border-box;background-color=
:transparent;color:inherit;text-decoration:inherit;word-break:break-word">F=
unctional Pearls</a></h4><p style=3D"box-sizing:border-box;margin:0px 0px 1=
0px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Ar=
ial,sans-serif;font-size:14px">A Functional Pearl is an elegant essay about=
something related to functional programming. Examples include, but are not=
limited to:</p><ul style=3D"box-sizing:border-box;margin-top:0px;margin-bo=
ttom:10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvet=
ica,Arial,sans-serif;font-size:14px"><li style=3D"box-sizing:border-box">a =
new and thought-provoking way of looking at an old idea;<ul style=3D"box-si=
zing:border-box;margin-top:0px;margin-bottom:0px"><li style=3D"box-sizing:b=
order-box">an instructive example of program calculation or proof;</li><li =
style=3D"box-sizing:border-box">a nifty presentation of an old or new data =
structure;</li><li style=3D"box-sizing:border-box">an interesting applicati=
on of functional programming techniques;</li><li style=3D"box-sizing:border=
-box">a novel use or exposition of functional programming in the classroom.=
</li></ul></li></ul><p style=3D"box-sizing:border-box;margin:0px 0px 10px;c=
olor:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,s=
ans-serif;font-size:14px">While pearls often demonstrate an idea through th=
e development of a short program, there is no requirement or expectation th=
at they do so. Thus, they encompass the notions of theoretical and educatio=
nal pearls.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:=
rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-s=
erif;font-size:14px">Functional Pearls are valued as highly and judged as r=
igorously as ordinary papers, but using somewhat different criteria. In par=
ticular, a pearl is not required to report original research, but, it shoul=
d be concise, instructive, and entertaining. A pearl is likely to be reject=
ed if its readers get bored, if the material gets too complicated, if too m=
uch-specialised knowledge is needed, or if the writing is inelegant. The ke=
y to writing a good pearl is polishing.</p><p style=3D"box-sizing:border-bo=
x;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue&=
quot;,Helvetica,Arial,sans-serif;font-size:14px">A submission that is inten=
ded to be treated as a pearl must be marked as such on the submission web p=
age and should contain the words =E2=80=9CFunctional Pearl=E2=80=9D somewhe=
re in its title or subtitle. These steps will alert reviewers to use the ap=
propriate evaluation criteria. Pearls will be combined with ordinary papers=
for the purpose of computing the conference=E2=80=99s acceptance rate.</p>=
<h4 style=3D"box-sizing:border-box;font-family:"Helvetica Neue",H=
elvetica,Arial,sans-serif;font-weight:500;line-height:1.1;color:rgb(51,51,5=
1);margin-top:10px;margin-bottom:10px;font-size:18px"><a href=3D"https://ic=
fp26.sigplan.org/track/icfp-2026-icfp-papers#experience-reports" id=3D"expe=
rience-reports" class=3D"gmail-anchor-link" style=3D"box-sizing:border-box;=
background-color:transparent;color:inherit;text-decoration:inherit;word-bre=
ak:break-word">Experience Reports</a></h4><p style=3D"box-sizing:border-box=
;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue&q=
uot;,Helvetica,Arial,sans-serif;font-size:14px">The purpose of an Experienc=
e Report is to describe the experience of using functional programming in p=
ractice, whether in industrial application, tool development, programming e=
ducation, or any other area.</p><p style=3D"box-sizing:border-box;margin:0p=
x 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helve=
tica,Arial,sans-serif;font-size:14px">Possible topics for an Experience Rep=
ort include, but are not limited to:</p><ul style=3D"box-sizing:border-box;=
margin-top:0px;margin-bottom:10px;color:rgb(51,51,51);font-family:"Hel=
vetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><li style=3D"b=
ox-sizing:border-box">insights gained from real-world projects using functi=
onal programming;<ul style=3D"box-sizing:border-box;margin-top:0px;margin-b=
ottom:0px"><li style=3D"box-sizing:border-box">comparison of functional pro=
gramming with conventional programming in the context of an industrial proj=
ect or a university curriculum project-management, business, or legal issue=
s encountered when using functional programming in a real-world project;</l=
i><li style=3D"box-sizing:border-box">curricular issues encountered when us=
ing functional programming in education;</li><li style=3D"box-sizing:border=
-box">real-world constraints that created special challenges for an impleme=
ntation of a functional language or for functional programming in general.<=
/li></ul></li></ul><p style=3D"box-sizing:border-box;margin:0px 0px 10px;co=
lor:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sa=
ns-serif;font-size:14px">An Experience Report is distinguished from a norma=
l PACMPL issue ICFP paper by its title, by its length, and by the criteria =
used to evaluate it.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10=
px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Ari=
al,sans-serif;font-size:14px">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 Experie=
nce Reports will be computed and reported separately from the rate for ordi=
nary papers.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color=
:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-=
serif;font-size:14px">Experience Report submissions can be at most 12 pages=
long, excluding bibliography.</p><p style=3D"box-sizing:border-box;margin:=
0px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Hel=
vetica,Arial,sans-serif;font-size:14px">Each accepted Experience Report wil=
l 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.</p><p style=3D"box-sizing:border-box;margin:0p=
x 0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helve=
tica,Arial,sans-serif;font-size:14px">Because the purpose of Experience Rep=
orts is to enable our community to understand the application of functional=
programming, an acceptable Experience Report need not add to the body of k=
nowledge of the functional-programming community by presenting novel result=
s or conclusions. It is sufficient if the report describes an illuminating =
experience with functional programming, or provides evidence for a clear th=
esis about the use of functional programming. The experience or thesis must=
be relevant to ICFP, but it need not be novel.</p><p style=3D"box-sizing:b=
order-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helveti=
ca Neue",Helvetica,Arial,sans-serif;font-size:14px">The review committ=
ee will accept or reject Experience Reports based on whether they judge the=
paper to illuminate some aspect of the use of functional programming. Anec=
dotal evidence will be acceptable provided it is well-argued and the author=
explains what efforts were made to gather as much evidence as possible. Ty=
pically, papers that show how functional programming was used are more conv=
incing than papers that say only that functional programming was used. It c=
an be especially effective to present comparisons of the situations before =
and after the experience described in the paper, but other kinds of evidenc=
e would also make sense, depending on context. Experience drawn from a sing=
le person=E2=80=99s experience may be sufficient, but more weight will be g=
iven to evidence drawn from the experience of groups of people.</p><p style=
=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-fami=
ly:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">An=
Experience Report should be short and to the point. For an industrial proj=
ect, it should make a claim about how well functional programming worked an=
d 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 work=
ed in this case in the same ways it has worked for others, the paper need o=
nly summarise the results =E2=80=94 the main part of the paper should discu=
ss how well it worked and in what context. Most readers will not want to kn=
ow all the details of the experience and its implementation, but the paper =
should characterise it and its context well enough so that readers can judg=
e to what degree this experience is relevant to their own circumstances. Th=
e paper should take care to highlight any unusual aspects; specifics about =
the experience are more valuable than generalities about functional program=
ming.</p><p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51=
,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;f=
ont-size:14px">If the paper not only describes experience but also presents=
new technical results, or if the experience refutes cherished beliefs of t=
he functional-programming community, it may be better to submit it as a ful=
l 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.</p><h2 style=3D"box-sizing:border-box;fo=
nt-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-weight=
:500;line-height:1.1;color:rgb(51,51,51);margin-top:20px;margin-bottom:10px=
;font-size:30px"><a href=3D"https://icfp26.sigplan.org/track/icfp-2026-icfp=
-papers#about-pacmpl" id=3D"gmail-about-pacmpl" class=3D"gmail-anchor-link"=
style=3D"box-sizing:border-box;background-color:transparent;color:inherit;=
text-decoration:inherit;word-break:break-word">About PACMPL</a></h2><p styl=
e=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);font-fam=
ily:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">P=
roceedings of the ACM on Programming Languages (PACMPL=C2=A0<a href=3D"http=
s://pacmpl.acm.org/" style=3D"box-sizing:border-box;background-color:transp=
arent;color:rgb(51,122,183);text-decoration-line:none;word-break:break-word=
">https://pacmpl.acm.org/</a>) is a Gold Open Access journal publishing res=
earch on all aspects of programming languages, from design to implementatio=
n and from mathematical formalisms to empirical studies. Each issue of the =
journal is devoted to a particular subject area within programming language=
s and will be announced through publicised Calls for Papers, like this one.=
</p><h3 style=3D"box-sizing:border-box;font-family:"Helvetica Neue&quo=
t;,Helvetica,Arial,sans-serif;font-weight:500;line-height:1.1;color:rgb(51,=
51,51);margin-top:20px;margin-bottom:10px;font-size:24px"><a href=3D"https:=
//icfp26.sigplan.org/track/icfp-2026-icfp-papers#important-update-on-acms-n=
ew-open-access-publishing-model-for-2026-acm-conferences" id=3D"gmail-impor=
tant-update-on-acms-new-open-access-publishing-model-for-2026-acm-conferenc=
es" class=3D"gmail-anchor-link" style=3D"box-sizing:border-box;background-c=
olor:transparent;color:inherit;text-decoration:inherit;word-break:break-wor=
d">Important update on ACM=E2=80=99s new open access publishing model for 2=
026 ACM Conferences:</a></h3><p style=3D"box-sizing:border-box;margin:0px 0=
px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetic=
a,Arial,sans-serif;font-size:14px">Starting January 1, 2026, ACM will fully=
transition to Open Access. All ACM publications, including those from ACM-=
sponsored conferences, will be 100% Open Access. Authors will have two prim=
ary options for publishing Open Access articles with ACM: the ACM Open inst=
itutional model or by paying Article Processing Charges (APCs). With over 1=
,800 institutions already part of ACM Open, the majority of ACM-sponsored c=
onference papers will not require APCs from authors or conferences (current=
ly, around 70=E2=80=9375%).</p><p style=3D"box-sizing:border-box;margin:0px=
0px 10px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvet=
ica,Arial,sans-serif;font-size:14px">Authors from institutions not particip=
ating in ACM Open will need to pay an APC to publish their papers, unless t=
hey qualify for a geographic or discretionary waiver. To find out whether a=
n APC applies to your article, please consult the list of=C2=A0<a href=3D"h=
ttps://libraries.acm.org/acmopen/open-participants" style=3D"box-sizing:bor=
der-box;background-color:transparent;color:rgb(51,122,183);text-decoration-=
line:none;word-break:break-word">participating institutions</a>=C2=A0in ACM=
Open and review the=C2=A0<a href=3D"https://www.acm.org/publications/polic=
ies/policy-on-open-access-apc-waivers-and-discounts" style=3D"box-sizing:bo=
rder-box;background-color:transparent;color:rgb(51,122,183);text-decoration=
-line:none;word-break:break-word">APC Waivers and Discounts Policy</a>.</p>=
<p style=3D"box-sizing:border-box;margin:0px 0px 10px;color:rgb(51,51,51);f=
ont-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:=
14px">To support a smooth transition and encourage broader ACM Open partici=
pation, ACM has introduced a temporary subsidy on APC pricing for 2026, fun=
ded directly by ACM. This pricing applies to all articles published in ACM =
and SIG sponsored conferences taking place in 2026. The subsidized conferen=
ce pricing for 2026 is as follows:</p><table style=3D"border-collapse:colla=
pse;border-spacing:0px;color:rgb(51,51,51);font-family:"Helvetica Neue=
",Helvetica,Arial,sans-serif;font-size:14px"><thead style=3D"box-sizin=
g:border-box"><tr style=3D"box-sizing:border-box"><th style=3D"box-sizing:b=
order-box;padding:2px 6px;text-align:left;border-top:1px solid rgb(204,204,=
204)">Authors</th><th style=3D"box-sizing:border-box;padding:2px 6px;text-a=
lign:left;border-top:1px solid rgb(204,204,204)">No ACM or SIG members</th>=
<th style=3D"box-sizing:border-box;padding:2px 6px;text-align:left;border-t=
op:1px solid rgb(204,204,204)">At least 1 ACM or SIG member</th></tr></thea=
d><tbody style=3D"box-sizing:border-box"><tr style=3D"box-sizing:border-box=
"><td style=3D"box-sizing:border-box;padding:2px 6px;border-top:1px solid r=
gb(204,204,204)">ACM and SIG Sponsored Conference Article</td><td style=3D"=
box-sizing:border-box;padding:2px 6px;border-top:1px solid rgb(204,204,204)=
">$350</td><td style=3D"box-sizing:border-box;padding:2px 6px;border-top:1p=
x solid rgb(204,204,204)">$250</td></tr><tr style=3D"box-sizing:border-box"=
><td style=3D"box-sizing:border-box;padding:2px 6px;border-top:1px solid rg=
b(204,204,204)">From a=C2=A0<a href=3D"https://www.acm.org/publications/pol=
icies/lower-middle-income-countries" style=3D"box-sizing:border-box;backgro=
und-color:transparent;color:rgb(51,122,183);text-decoration-line:none;word-=
break:break-word">lower-middle-income country</a></td><td style=3D"box-sizi=
ng:border-box;padding:2px 6px;border-top:1px solid rgb(204,204,204)">$175</=
td><td style=3D"box-sizing:border-box;padding:2px 6px;border-top:1px solid =
rgb(204,204,204)">$125</td></tr></tbody></table><p style=3D"box-sizing:bord=
er-box;margin:0px 0px 10px;color:rgb(51,51,51);font-family:"Helvetica =
Neue",Helvetica,Arial,sans-serif;font-size:14px">This represents a=C2=
=A0<a href=3D"https://www.acm.org/publications/openaccess" style=3D"box-siz=
ing:border-box;background-color:transparent;color:rgb(51,122,183);text-deco=
ration-line:none;word-break:break-word">65% discount</a>, funded directly b=
y ACM. Authors are encouraged to help advocate for their institutions to jo=
in ACM Open during this transition period.</p></div>
--000000000000098168064354a26a--