From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by c5ff346549e7 (Postfix) with ESMTPS id 19B545D4 for ; Tue, 2 Feb 2021 15:57:43 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.79,395,1602540000"; d="scan'208";a="490451529" Received: from prod-listesu18.inria.fr (HELO sympa.inria.fr) ([128.93.162.160]) by mail2-relais-roc.national.inria.fr with ESMTP; 02 Feb 2021 16:57:27 +0100 Received: by sympa.inria.fr (Postfix, from userid 20132) id 44BC8E0A9B; Tue, 2 Feb 2021 16:57:27 +0100 (CET) Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id D8D77E03B6 for ; Tue, 2 Feb 2021 16:57:20 +0100 (CET) Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=icfp.publicity@googlemail.com; spf=Pass smtp.mailfrom=icfp.publicity@googlemail.com; spf=None smtp.helo=postmaster@mail-il1-f180.google.com IronPort-PHdr: =?us-ascii?q?9a23=3A7T1YJxCyPBZUFxiaRp13UyQJP3N1i/DPJgcQr6Af?= =?us-ascii?q?oPdwSP37osmwAkXT6L1XgUPTWs2DsrQY0ruQ7/irBDNIoc7Y9ixbL9oUD15NoP?= =?us-ascii?q?5VtjRoONSCB0z/IayiRA0BN+MGamVY+WqmO1NeAsf0ag6aiHSz6TkPBke3blIt?= =?us-ascii?q?daz6FYHIksu4yf259YHNbAVUnjq9Zq55IAmroQnLucQanI9vJrw+xxfVrXdFe+?= =?us-ascii?q?Zbzn5sKV6Pghrw/Mi98INh/ihKp/4t68tMWrjmcqolSrBVEC4oOH0v6s3xshnD?= =?us-ascii?q?QwqP5n8CXWgTjxFFHQvL4gzkU5noqif1ufZz1yecPc3tULA7Qi+i4LtxSB/pky?= =?us-ascii?q?gIKTg0+3zKh8NqjaJbpBWhpwFjw4PRfYqYOuZycr/bcNgHQ2dKQ8RfWDFbAo6k?= =?us-ascii?q?b4UBAfQPM+VFoYbyu1QAogCzBRW1BO711jNEmmP60K883u88EQ/GxgsgH9cWvX?= =?us-ascii?q?rJttr1MboZX/6yzKbTzDXDaepa1zX66IfUchAhuu2MUqhtfsrN1EIiEALFgUme?= =?us-ascii?q?qYz9JT+VzvkNvHOf7+phSe2vinInqgFqrzigwccsjYbJhoYLxVDB7yp5wYI1Kc?= =?us-ascii?q?ekR058ZN6pCZ1dvDyVOIVqWM0tWX1ouDokxb0cv562ZCwHxYkjyhPdZfGKcIaF?= =?us-ascii?q?7BzsWuuPITl1mH1odbCxiRqv80Wtyu7xW8aw3VpWridIkd3BuHAN2hHR6cWKV/?= =?us-ascii?q?Rz81qn1D2S2Q7T7eRELlo1lardM5Mh2b8wlpULsUTHBCD2nl/6jKiMdkUr4uSo?= =?us-ascii?q?6+PnYqn6qZ+GL494kB3xMqMrmsCnG+s3Lg0OU3Kc+eSm273v5VH5QLRPjvIoiK?= =?us-ascii?q?bZto3VKtkBqa6lHQBZyJos6xG6Dzu+19QXh2IHLEpfdx6diIjpIV7OLfblBvm8?= =?us-ascii?q?m1ShiClny+zCM7H7AZjALmLPnKrgcLt88UJQ1Qk+wcxH659VCbwNOv3+V0/ruN?= =?us-ascii?q?HaEBM1KRG4zun7BNh7y4gQQ3iAArWDP6PXqVKI5vwgI+2LZIINvTbyMfkl5/r3?= =?us-ascii?q?gX84nV8RYLCl3ZUKZH27AvhqOUqZYX3rgtcOFWcFoBAyQ/DtiF2HSTJTZnCyUL?= =?us-ascii?q?wg5jwjFo6qEYPOSpqujbGBxiu3A5xba2FcBlyREnrka52IW/IWZyKTJs9hnCYE?= =?us-ascii?q?Vb+kS4I51BGhqAH6y6J9IurM5y0Xrpbj1Nlp6O3SiREz9Sd5D8ua02GKQGF0mn?= =?us-ascii?q?0HRzos06B+pUxx0EuM0a99g/BAD9xc++tJUhsmNZ7b1+F1F8r9WgfFftuQTFam?= =?us-ascii?q?Q86mAS0qQ9Iqw94OZl59FM+4ghDC2SqqGb4VmKaRCJw66KKPl0T2cs10znKD0K?= =?us-ascii?q?g6k3EnRNFOPCuonP1R7Q/WUrXAlg2lkKyrc+E82yXN73uKwXbG6EBTXhY2SbjP?= =?us-ascii?q?WXEUZ1fHhdv+4UzGQrqnCLBhOQxEn53RYpBWY8Hk2A0VDMzoP87TNjroxzWAQC?= =?us-ascii?q?2Qz7bJV7LEPn0H1XyDWkcDlA8X8HOPNAx4DSCk8TqHXW5eUGn3akapytFQ7Xay?= =?us-ascii?q?T0s61QaPNhMz2L2y9RoYgPWdT7UY2bdW4X58+QUxJ0602pftM/TFpwdle/8CM9?= =?us-ascii?q?Y04VMC1GaA8gIkbsTmIKdliVoTNQ9wuhG22g=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAwDMdRlgf7SmVdFYAQMGgQmBUYF0B?= =?us-ascii?q?oEXDldmhECJBIhSjxaLSIFoCAMBAwELAQEjCgIEAQGBVYIxgkICHQcBBDQTAhA?= =?us-ascii?q?BAQUBAQECAQMDBAETAQENCwsIJ4U9CCUNQwEQAYFjIoMyCAMGHQElAgQGAgYDE?= =?us-ascii?q?h8CJgI2AQUBLBILAgxTgWZMglQBAwklD6MFgQQ9iWgDAhU8doEygwYGgUsPgn0?= =?us-ascii?q?KQQ2CHQIHCQEIJQFWKgGNPhYQgRSBB4EQAYNXgQQ9gRELBIEgBwkBAwEYgymCY?= =?us-ascii?q?ASBVAEICAoSPw4QEwcaDAkDBAsNChkIDwETDQItDigHBAEHBRcNAQoDAQkFBgM?= =?us-ascii?q?DGAEFCgEBFwUGAwELL4xUgm0ZASEHimaBdYEZiQ2QK4EUB4J7BIdVgV2STCKDL?= =?us-ascii?q?4EziRGFLT6JSIV2nmN1kUcoAhMJhDgCCgcGECOBSoF6NBkjLyGCaQlHGQ1XiD+?= =?us-ascii?q?FI4ENAQIGgkOFFIViIzMCNQIGAQkBAQMJWIIKhm0BAQ8XB4IXAQE?= X-IPAS-Result: =?us-ascii?q?A0AlAwDMdRlgf7SmVdFYAQMGgQmBUYF0BoEXDldmhECJBIh?= =?us-ascii?q?SjxaLSIFoCAMBAwELAQEjCgIEAQGBVYIxgkICHQcBBDQTAhABAQUBAQECAQMDB?= =?us-ascii?q?AETAQENCwsIJ4U9CCUNQwEQAYFjIoMyCAMGHQElAgQGAgYDEh8CJgI2AQUBLBI?= =?us-ascii?q?LAgxTgWZMglQBAwklD6MFgQQ9iWgDAhU8doEygwYGgUsPgn0KQQ2CHQIHCQEIJ?= =?us-ascii?q?QFWKgGNPhYQgRSBB4EQAYNXgQQ9gRELBIEgBwkBAwEYgymCYASBVAEICAoSPw4?= =?us-ascii?q?QEwcaDAkDBAsNChkIDwETDQItDigHBAEHBRcNAQoDAQkFBgMDGAEFCgEBFwUGA?= =?us-ascii?q?wELL4xUgm0ZASEHimaBdYEZiQ2QK4EUB4J7BIdVgV2STCKDL4EziRGFLT6JSIV?= =?us-ascii?q?2nmN1kUcoAhMJhDgCCgcGECOBSoF6NBkjLyGCaQlHGQ1XiD+FI4ENAQIGgkOFF?= =?us-ascii?q?IViIzMCNQIGAQkBAQMJWIIKhm0BAQ8XB4IXAQE?= X-IronPort-AV: E=Sophos;i="5.79,395,1602540000"; d="scan'208";a="371879636" X-MGA-submission: =?us-ascii?q?MDGAF8GyTPPnt/od821VAXE3PEC+ynePEF2JT0?= =?us-ascii?q?alJ7v8gykvQ7HmepV+JNY4lfrUGX+QpaylV6kwH+LAr0He5ObGIqR/Yq?= =?us-ascii?q?Bkp55XIHhij54ZFPaIJq2h5Ht0tx6KK09a5GFlKVIdaUnFBTq5jkc/NN?= =?us-ascii?q?/jiP/BrKECTB513x0VYY5TWQ=3D=3D?= Received: from mail-il1-f180.google.com ([209.85.166.180]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES256-GCM-SHA384; 02 Feb 2021 16:57:18 +0100 Received: by mail-il1-f180.google.com with SMTP id z18so19243382ile.9 for ; Tue, 02 Feb 2021 07:57:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=from:date:to:message-id:subject:mime-version :content-transfer-encoding; bh=ZIDuaqHCGPLxEoxyax1SQqB8xhmWSLRK9wSeM5MRKOs=; b=lFGOjfcazcFfiT4FKFLtY+59N8Jub8P09QtEvsBuRvhiMZQmbBqUwPFPrxImhZ5dS8 L98jUb3P254qt+JiKHUnT+bN6fgkgjlPkiN7djeS+3SeFE6CaD0wG22CqQx1uPpB1NUx jI3xMvzbOd88+VyolLvtZ9uw6zwl4EQ0WbkHKQaUoIG06gsl8w+DKm5r1inwKXrHDnyl FSVlDKhGlULXZZ8T6CvWpkJQB7DLNj9w6BjB4zF/a5ohluF3ddJxi0scYwSg0ahP4QUu G1+rfZxYjvG246CrRgqg3MczVOJIxiAYUBZXQcXm6rr/SPJGKFEdgEuCgW9iKaaqxN2m vekA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:message-id:subject:mime-version :content-transfer-encoding; bh=ZIDuaqHCGPLxEoxyax1SQqB8xhmWSLRK9wSeM5MRKOs=; b=CytUzdve42jkSxkXUYnn52P8/N53rW2UIxp3FXFhaqHS6ggxJRhYuokv9BqXVUGkyi ZE6CaLuxltZMPlBGbZ3Gm7oXQ0qp5OK/eHXbcO4YEI0Zj6RiIVeuZPA2uFuFXfbfcKuH ymXuwdjRjUbry07AX2E6GQEz77A7JSDcyiGreicE12Xx7m5+9c/sWPuvmdB1478Ga8gG 3ahZBcyOR9u1jB90rHgYAZ9BAhLGCEVBlHg0P+A3IUiokoiyOn8Dd+4guLGoXskON3BP NTL7VSmHEYKhutpD57jQzHs1iehYnf9eoN2l2w8YHU3ezyYxfNdu48ULptU7VfZ543me 2EyA== X-Gm-Message-State: AOAM530+F5eUirVlF9CcWFe0FPI7Ke08Cp75UjCl9sLZ6IEaqhKRZDBN 3OlxUdnlpX+yHHAa70ViOl54DJGHisA= X-Google-Smtp-Source: ABdhPJwJj26ODzeId74Y2OGh/rmDeGULgJVIUlgBtxyLqdguu6QpRx3ceeOzKZfbhYNooJxjLb/RvQ== X-Received: by 2002:a05:6e02:1bec:: with SMTP id y12mr18022069ilv.214.1612281436621; Tue, 02 Feb 2021 07:57:16 -0800 (PST) Received: from icfp.publicity (c-68-45-72-140.hsd1.in.comcast.net. [68.45.72.140]) by smtp.gmail.com with ESMTPSA id y25sm10272856ioa.5.2021.02.02.07.57.15 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Feb 2021 07:57:15 -0800 (PST) From: Sam Tobin-Hochstadt X-Google-Original-From: Sam Tobin-Hochstadt Date: Tue, 02 Feb 2021 10:57:15 -0500 To: caml-list@inria.fr Message-ID: <6019765b92be0_c46e221c04e@homer.mail> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Caml-list] Call for Papers: PACMPL issue ICFP 2021 Reply-To: Sam Tobin-Hochstadt X-Loop: caml-list@inria.fr X-Sequence: 18396 Errors-To: caml-list-owner@inria.fr Precedence: list Precedence: bulk Sender: caml-list-request@inria.fr X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: Archived-At: =0D PACMPL Volume 5, Issue ICFP 2021=0D Call for Papers=0D =0D Accepted papers to be invited for presentation at=0D The 26th ACM SIGPLAN International Conference on Functional Programming=0D= To Be Held Virtualy=0D http://icfp21.sigplan.org/=0D =0D ### Important dates=0D =0D Submissions due: 2 March 2021 (Tuesday) Anywhere on Earth=0D https://icfp21.hotcrp.com=0D Author response: 20 April (Tuesday) - 23 April (Friday) 17:00 UTC=0D Notification: 7 May (Friday)=0D Final copy due: 30 June (Wednesday)=0D Conference: 22 August (Sunday) - 27 August (Friday)=0D =0D ### About PACMPL=0D =0D Proceedings of the ACM on Programming Languages (PACMPL=0D ) is a Gold Open Access journal publishing=0D research on all aspects of programming languages, from design to=0D implementation and from mathematical formalisms to empirical=0D studies. Each issue of the journal is devoted to a particular subject=0D area within programming languages and will be announced through=0D publicized Calls for Papers, like this one.=0D =0D ### Scope=0D =0D [PACMPL](https://pacmpl.acm.org/) issue ICFP 2021 seeks original=0D papers on the art and science of functional programming. Submissions=0D are invited on all topics from principles to practice, from=0D foundations to features, and from abstraction to application. The=0D scope includes all languages that encourage functional programming,=0D including both purely applicative and imperative languages, as well as=0D= languages with objects, concurrency, or parallelism. Topics of=0D interest include (but are not limited to):=0D =0D * Language Design: concurrency, parallelism, and distribution;=0D modules; components and composition; metaprogramming; macros;=0D pattern matching; type systems; type inference; dependent types;=0D session types; gradual typing; refinement types; interoperability;=0D domain-specific languages; imperative programming; object-oriented=0D programming; logic programming; probabilistic programming;=0D reactive programming; generic programming; bidirectional=0D programming.=0D =0D * Implementation: abstract machines; virtual machines;=0D interpretation; compilation; compile-time and run-time=0D optimization; garbage collection and memory management; runtime=0D systems; multi-threading; exploiting parallel hardware; interfaces=0D to foreign functions, services, components, or low-level machine=0D resources.=0D =0D * Software-Development Techniques: algorithms and data structures;=0D design patterns; specification; verification; validation; proof=0D assistants; debugging; testing; tracing; profiling; build systems;=0D program synthesis.=0D =0D * Foundations: formal semantics; lambda calculus; program=0D equivalence; rewriting; type theory; logic; category theory;=0D monads; continuations; control; state; effects; names and binding;=0D program verification.=0D =0D * Analysis and Transformation: control flow; data flow; abstract=0D interpretation; partial evaluation; program calculation.=0D =0D * Applications: symbolic computing; formal-methods tools; artificial=0D intelligence; systems programming; distributed systems and web=0D programming; hardware design; databases; XML processing;=0D scientific and numerical computing; graphical user interfaces;=0D graphics and multimedia; GPU programming; scripting; system=0D administration; security.=0D =0D * Education: teaching introductory programming; parallel=0D programming; mathematical proof; algebra.=0D =0D Submissions will be evaluated according to their relevance,=0D correctness, significance, originality, and clarity. Each submission=0D should explain its contributions in both general and technical terms,=0D clearly identifying what has been accomplished, explaining why it is=0D significant, and comparing it with previous work. The technical=0D content should be accessible to a broad audience.=0D =0D PACMPL issue ICFP 2021 also welcomes submissions in two separate=0D categories =E2=80=94 Functional Pearls and Experience Reports =E2=80=94 t= hat must be=0D marked as such when submitted and that need not report original=0D research results. Detailed guidelines on both categories are given at=0D the end of this call.=0D =0D Please contact the associate editor if you have questions or are=0D concerned about the appropriateness of a topic.=0D =0D =0D ### Preparation of submissions=0D =0D **Deadline**: The deadline for submissions is **Tuesday, March 2, 2021**,= =0D Anywhere on Earth ().=0D This deadline will be strictly enforced.=0D =0D **Formatting**: Submissions must be in PDF format, printable in black=0D and white on US Letter sized paper, and interpretable by common PDF=0D tools. All submissions must adhere to the "ACM Small" template that is=0D= available (in both LaTeX and Word formats) from=0D . =0D =0D There is a limit of **25 pages for a full paper or Functional Pearl**=0D and **12 pages for an Experience Report**; in either case, the=0D bibliography will not be counted against these limits. Submissions=0D that exceed the page limits or, for other reasons, do not meet the=0D requirements for formatting, will be summarily rejected. Supplementary=0D= material can and should be **separately** submitted (see below).=0D =0D See also PACMPL's Information and Guidelines for Authors at=0D .=0D =0D **Submission**: Submissions will be accepted at =0D =0D Improved versions of a paper may be submitted at any point before the=0D submission deadline using the same web interface.=0D =0D **Author Response Period**: Authors will have a 72-hour period,=0D starting at 17:00 UTC on **Tuesday, April 20, 2021**, to read reviews=0D and respond to them.=0D =0D **Supplementary Material**: Authors have the option to attach=0D supplementary material to a submission, on the understanding that=0D reviewers may choose not to look at it. This supplementary material=0D should **not** be submitted as part of the main document; instead, it=0D should be uploaded as a **separate** PDF document or tarball.=0D =0D Supplementary material should be uploaded **at submission time**, not=0D by providing a URL in the paper that points to an external repository.=0D= =0D Authors are free to upload both anonymized and non-anonymized=0D supplementary material. Anonymized supplementary material will be=0D visible to reviewers immediately; non-anonymized supplementary=0D material will be revealed to reviewers only after they have submitted=0D their review of the paper and learned the identity of the author(s).=0D =0D **Authorship Policies**: All submissions are expected to comply with=0D the ACM Policies for Authorship that are detailed at=0D .=0D =0D **Republication Policies**: Each submission must adhere to SIGPLAN's=0D republication policy, as explained on the web at=0D .=0D =0D ### Review Process=0D =0D This section outlines the two-stage process with lightweight=0D double-blind reviewing that will be used to select papers for PACMPL=0D issue ICFP 2021. We anticipate that there will be a need to clarify=0D and expand on this process, and we will maintain a list of frequently=0D asked questions and answers on the PACMPL issue website to address=0D common concerns.=0D =0D **PACMPL issue ICFP 2021 will employ a two-stage review process.** The=0D= first stage in the review process will assess submitted papers using=0D the criteria stated above and will allow for feedback and input on=0D initial reviews through the author response period mentioned=0D previously. As a result of the review process, a set of papers will be=0D= conditionally accepted and all other papers will be rejected.=0D Authors will be notified of these decisions on **May 7, 2021**.=0D =0D Authors of conditionally accepted papers will be provided with=0D committee reviews along with a set of mandatory revisions. After four=0D weeks (June 4, 2021), the authors will provide a second=0D submission. The second and final reviewing phase assesses whether the=0D mandatory revisions have been adequately addressed by the authors and=0D thereby determines the final accept/reject status of the paper. The=0D intent and expectation is that the mandatory revisions can be=0D addressed within four weeks and hence that conditionally accepted=0D papers will in general be accepted in the second phase.=0D =0D The second submission should clearly identify how the mandatory=0D revisions were addressed. To that end, the second submission must be=0D accompanied by a cover letter mapping each mandatory revision request=0D to specific parts of the paper. The cover letter will facilitate a=0D quick second review, allowing for confirmation of final acceptance=0D within two weeks. Conversely, the absence of a cover letter will be=0D grounds for the paper=E2=80=99s rejection.=0D =0D **PACMPL issue ICFP 2021 will employ a lightweight double-blind=0D reviewing process.** To facilitate this, submitted papers must=0D adhere to two rules:=0D =0D 1. **author names and institutions must be omitted**, and=0D 2. **references to authors' own related work should be in the third=0D person** (e.g., not "We build on our previous work ..." but rather=0D "We build on the work of ...").=0D =0D The purpose of this process is to help the reviewers come to an=0D initial judgement about the paper without bias, not to make it=0D impossible for them to discover the authors if they were to=0D try. Nothing should be done in the name of anonymity that weakens the=0D submission or makes the job of reviewing the paper more difficult=0D (e.g., important background references should not be omitted or=0D anonymized). In addition, authors should feel free to disseminate=0D their ideas or draft versions of their paper as they normally=0D would. For instance, authors may post drafts of their papers on the=0D web or give talks on their research ideas.=0D =0D ### Information for Authors of Accepted Papers=0D =0D * As a condition of acceptance, final versions of all papers must=0D adhere to the new ACM Small format. The page limit for the final=0D versions of papers will be increased by two pages to help authors=0D respond to reviewer comments and mandatory revisions: **27 pages=0D plus bibliography for a regular paper or Functional Pearl, 14 pages=0D plus bibliography for an Experience Report**.=0D =0D * Authors of accepted submissions will be required to agree to one of=0D the three ACM licensing options: open access on payment of a fee=0D (**recommended**, and SIGPLAN can cover the cost as described next);=0D copyright transfer to ACM; or retaining copyright but granting ACM=0D exclusive publication rights. Further information about ACM author=0D rights is available from .=0D =0D * PACMPL is a Gold Open Access journal, and authors are encouraged to=0D publish their work under a CC-BY license. Gold Open Access=0D guarantees permanent free online access to the definitive version in=0D= the ACM Digital Library, and the recommended CC-BY option also=0D allows anyone to copy and distribute the work with attribution.=0D Gold Open Access has been made possible by generous funding through=0D ACM SIGPLAN, which will cover all open access costs in the event=0D authors cannot. Authors who can cover the costs may do so by paying=0D an Article Processing Charge (APC). PACMPL, SIGPLAN, and ACM=0D Headquarters are committed to exploring routes to making Gold Open=0D Access publication both affordable and sustainable.=0D =0D * ACM offers authors a range of copyright options, one of which is=0D Creative Commons CC-BY publication; this is the option recommended=0D by the PACMPL editorial board. A reasoned argument in favour of this=0D option can be found in the article [Why=0D CC-BY?](https://oaspa.org/why-cc-by/) published by OASPA, the Open=0D Access Scholarly Publishers Association.=0D =0D * ACM Author-Izer is a unique service that enables ACM authors to=0D generate and post links on either their home page or institutional=0D repository for visitors to download the definitive version of their=0D articles from the ACM Digital Library at no charge. Downloads=0D through Author-Izer links are captured in official ACM statistics,=0D improving the accuracy of usage and impact=0D measurements. Consistently linking to the definitive version of an=0D ACM article should reduce user confusion over article=0D versioning. After an article has been published and assigned to the=0D appropriate ACM Author Profile pages, authors should visit=0D to learn=0D how to create links for free downloads from the ACM DL.=0D =0D * The official publication date is the date the papers are made=0D available in the ACM Digital Library. This date may be up to *two=0D weeks prior* to the first day of the conference. The official=0D publication date affects the deadline for any patent filings related=0D to published work.=0D =0D * Authors of each accepted submission are invited to attend and be=0D available for the presentation of that paper at the conference. The=0D schedule for presentations will be determined and shared with authors=0D= after the full program has been selected.=0D =0D =0D =0D ### Artifact Evaluation=0D =0D Authors of papers that are conditionally accepted in the first phase=0D of the review process will be encouraged (but not required) to submit=0D supporting materials for Artifact Evaluation. These items will then be=0D= reviewed by an Artifact Evaluation Committee, separate from the paper=0D Review Committee, whose task is to assess how the artifacts support=0D the work described in the associated paper. Papers that go through the=0D= Artifact Evaluation process successfully will receive a seal of=0D approval printed on the papers themselves. Authors of accepted papers=0D will be encouraged to make the supporting materials publicly available=0D= upon publication of the papers, for example, by including them as=0D "source materials" in the ACM Digital Library. An additional seal=0D will mark papers whose artifacts are made available, as outlined in=0D the ACM guidelines for artifact badging.=0D =0D Participation in Artifact Evaluation is voluntary and will not=0D influence the final decision regarding paper acceptance.=0D =0D ### Special categories of papers=0D =0D In addition to research papers, PACMPL issue ICFP solicits two kinds=0D of papers that do not require original research contributions:=0D Functional Pearls, which are full papers, and Experience Reports,=0D which are limited to half the length of a full paper. Authors=0D submitting such papers should consider the following guidelines.=0D =0D #### Functional Pearls=0D =0D A Functional Pearl is an elegant essay about something related to=0D functional programming. Examples include, but are not limited to:=0D =0D * a new and thought-provoking way of looking at an old idea=0D =0D * an instructive example of program calculation or proof=0D =0D * a nifty presentation of an old or new data structure=0D =0D * an interesting application of functional programming techniques=0D =0D * a novel use or exposition of functional programming in the classroom=0D= =0D While pearls often demonstrate an idea through the development of a=0D short program, there is no requirement or expectation that they do=0D so. Thus, they encompass the notions of theoretical and educational=0D pearls.=0D =0D Functional Pearls are valued as highly and judged as rigorously as=0D ordinary papers, but using somewhat different criteria. In particular,=0D= a pearl is not required to report original research, but, it should be=0D= concise, instructive, and entertaining. A pearl is likely to be=0D rejected if its readers get bored, if the material gets too=0D complicated, if too much specialized knowledge is needed, or if the=0D writing is inelegant. The key to writing a good pearl is polishing.=0D =0D A submission that is intended to be treated as a pearl must be marked=0D as such on the submission web page, and should contain the words=0D "Functional Pearl" somewhere in its title or subtitle. These steps=0D will alert reviewers to use the appropriate evaluation=0D criteria. Pearls will be combined with ordinary papers, however, for=0D the purpose of computing the conference's acceptance rate.=0D =0D #### Experience Reports=0D =0D The purpose of an Experience Report is to help create a body of=0D published, refereed, citable evidence that functional programming=0D really works -- or to describe what obstacles prevent it from=0D working.=0D =0D Possible topics for an Experience Report include, but are not limited to:= =0D =0D * insights gained from real-world projects using functional programming=0D= =0D * comparison of functional programming with conventional programming=0D in the context of an industrial project or a university curriculum=0D =0D * project-management, business, or legal issues encountered when=0D using functional programming in a real-world project=0D =0D * curricular issues encountered when using functional programming in=0D education=0D =0D * real-world constraints that created special challenges for an=0D implementation of a functional language or for functional=0D programming in general=0D =0D An Experience Report is distinguished from a normal PACMPL issue ICFP=0D paper by its title, by its length, and by the criteria used to=0D evaluate it.=0D =0D * Both in the papers and in any citations, the title of each=0D accepted Experience Report must end with the words "(Experience=0D Report)" in parentheses. The acceptance rate for Experience=0D Reports will be computed and reported separately from the rate for=0D ordinary papers.=0D =0D * Experience Report submissions can be at most 12 pages long,=0D excluding bibliography.=0D =0D * Each Experience Report accepted to the PACMPL issue will be=0D presented at the conference, but depending on the number of=0D Experience Reports and regular papers accepted, authors of=0D Experience reports may be asked to give shorter talks.=0D =0D * Because the purpose of Experience Reports is to enable our=0D community to accumulate a body of evidence about the efficacy of=0D functional programming, an acceptable Experience Report need not=0D add to the body of knowledge of the functional-programming=0D community by presenting novel results or conclusions. It is=0D sufficient if the Report states a clear thesis and provides=0D supporting evidence. The thesis must be relevant to the PACMPL=0D issue, but it need not be novel.=0D =0D The review committee will accept or reject Experience Reports based on=0D= whether they judge the evidence to be convincing. Anecdotal evidence=0D will be acceptable provided it is well argued and the author explains=0D what efforts were made to gather as much evidence as=0D possible. Typically, more convincing evidence is obtained from papers=0D which show how functional programming was used than from papers which=0D only say that functional programming was used. The most convincing=0D evidence often includes comparisons of situations before and after the=0D= introduction or discontinuation of functional programming. Evidence=0D drawn from a single person's experience may be sufficient, but more=0D weight will be given to evidence drawn from the experience of groups=0D of people.=0D =0D An Experience Report should be short and to the point: it should make=0D a claim about how well functional programming worked on a particular=0D project and why, and produce evidence to substantiate this claim. If=0D functional programming worked in this case in the same ways it has=0D worked for others, the paper need only summarize the results;=0D the main part of the paper should discuss how well it worked and in=0D what context. Most readers will not want to know all the details of=0D the project and its implementation, but the paper should characterize=0D the project and its context well enough so that readers can judge to=0D what degree this experience is relevant to their own projects. The=0D paper should take care to highlight any unusual aspects of the=0D project. Specifics about the project are more valuable than=0D generalities about functional programming; for example, it is more=0D valuable to say that the team delivered its software a month ahead of=0D schedule than it is to say that functional programming made the team=0D more productive.=0D =0D If the paper not only describes experience but also presents new=0D technical results, or if the experience refutes cherished beliefs of=0D the functional-programming community, it may be better to submit it as=0D= a full paper, which will be judged by the usual criteria of novelty,=0D originality, and relevance. The associate editor will be happy to=0D advise on any concerns about which category to submit to.=0D =0D =0D =0D ### ICFP Organizers=0D =0D General Chair: Sukyoung Ryu (KAIST, South Korea)=0D =0D Accessibility Co-Chairs: Lindsey Kuper (UC Santa Cruz, USA), Kathrin=0D Stark (Princeton University, USA)=0D Artifact Evaluation Co-Chairs: Gabriel Scherer (INRIA Saclay, France),=0D= Brent Yorgey (Hendrix College, USA)=0D Industrial Relations Co-Chairs: Alan Jeffrey (Roblox, USA),=0D Simon Marlow (Facebook, England)=0D Programming Contest Co-Organisers: Alex Lang, Jasper Van der Jeugt=0D (Fugue, Switzerland)=0D Publicity and Web Chair: Sam Tobin-Hochstadt (Indiana University, USA)=0D= Student Research Competition Chair: Anders Miltner (University of=0D Texas, USA)=0D Student Volunteer Co-Chairs: Lily Bryant (University of British=0D Columbia, Canada), Jaemin Hong (KAIST, South Korea), Hanneli Tavante=0D (McGill University, Canada)=0D Video Co-Chairs: Leif Andersen (Northeastern University, USA),=0D Benjamin Chung (Northeastern University, USA)=0D Workshops Co-Chairs: Leonidas Lampropoulos (University of Maryland, USA),= =0D Zoe Paraskevopoulou (Princeton University, USA)=0D =0D =0D =0D ### PACMPL Volume 5, Issue ICFP 2021=0D =0D Associate Editor: Ronald Garcia, (University of British Columbia, Canada)= =0D =0D Review Committee:=0D =0D Zena Ariola (University of Oregon, USA)=0D Stephanie Balzer (Carnegie Mellon University, USA)=0D Matteo Cimini (UMass Lowell, USA)=0D Youyou Cong (Tokyo Institute of Technology, Japan)=0D Harley Eades (University of Augusta, USA)=0D Andrew Gordon (Microsoft Research & University of Edinburgh, United Kingd= om)=0D Benjamin Greenman (Brown University, USA)=0D Arjun Guha (Northeastern University, USA)=0D Jurriaan Hage (Utrecht, The Netherlands)=0D Favonia (University of Minnesota, USA)=0D Suresh Jagannathan (Purdue University, USA)=0D Patricia Johann (Appalachian State University, USA)=0D Ralf Jung (Max Planck Institute, Germany)=0D Ekaterina Komendantskaya (Heriot-Watt, Scotland)=0D Leonidas Lampropoulos (University of Maryland, USA)=0D Kazutaka Matsuda (Tohoku University, Japan)=0D Akimasa Morihata (Univeristy of Tokyo, Japan)=0D Stefan Muller (Illinois Institute of Technology, USA)=0D Max New (Wesleyan University, USA)=0D Rishiyur Nikhil (Bluespec , USA)=0D Cyrus Omar (University of Michigan, USA)=0D Brigitte Pientka (McGill University, Canada)=0D Norman Ramsey (Tufts University, USA)=0D Christine Rizkallah (University of New South Wales, Australia)=0D Taro Sekiyama (National Institute for Informatics, Japan)=0D Eijiro Sumii (Tohoku University, Japan)=0D Amin Timany (Aarhus University, Denmark)=0D Mitchell Wand (Northeastern University, USA)=0D Steve Zdancewic (University of Pennsylvania, USA)=0D