From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 4D12F82581 for ; Wed, 13 Feb 2019 19:14:49 +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-it1-f193.google.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of icfp.publicity@googlemail.com) identity=pra; client-ip=209.85.166.193; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="icfp.publicity@googlemail.com"; x-sender="icfp.publicity@googlemail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of icfp.publicity@googlemail.com designates 209.85.166.193 as permitted sender) identity=mailfrom; client-ip=209.85.166.193; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="icfp.publicity@googlemail.com"; x-sender="icfp.publicity@googlemail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-it1-f193.google.com) identity=helo; client-ip=209.85.166.193; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="icfp.publicity@googlemail.com"; x-sender="postmaster@mail-it1-f193.google.com"; x-conformance=sidf_compatible IronPort-PHdr: =?us-ascii?q?9a23=3AICU/fBcvR6nGdGbKiipl0rDElGMj4u6mDksu8pMi?= =?us-ascii?q?zoh2WeGdxcW8Yh7h7PlgxGXEQZ/co6odzbaO4+a4ASQp2tWoiDg6aptCVhsI24?= =?us-ascii?q?09vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7?= =?us-ascii?q?Ovr6GpLIj8Swyuu+54Dfbx9HiTahYr5+Ngm6oRnMvcQKnIVuLbo8xAHUqXVSYe?= =?us-ascii?q?RWwm1oJVOXnxni48q74YBu/SdNtf8/7sBMSar1cbg2QrxeFzQmLns65Nb3uhnZ?= =?us-ascii?q?TAuA/WUTX2MLmRdVGQfF7RX6XpDssivms+d2xSeXMdHqQb0yRD+v6bpgRh31hy?= =?us-ascii?q?cdLzM38G/ZhNJzgqxGrx2uuxNxzpXIYIGMLvdyYr/Rcc8YSGdHQ81fVzZBAoS5?= =?us-ascii?q?b4YXEuQOJ+NYpJTjqVsJthS+BA+sCPrtxD9PmnD23bY60/g7Hg7bwAwrAtUDsH?= =?us-ascii?q?XIo9X7LKceS/i1zLTTwjXHbvNZxTb96JTIcx06rvGMWrVwccXVyUYxEgPKlFSQ?= =?us-ascii?q?qYj/MzyJ0eQNtnGW4ux9XuyhjG4nrht+ojmpxso0kIbGmocVxkrD9SVjz4Y5Pc?= =?us-ascii?q?a4SE90Yd68FJtfrSeaO5FxQsM4TGFkoCg7yrwFuZ66ZCgF1okoxx/FZPCddIiI?= =?us-ascii?q?+B3jWP6RITd/mHJqZKi/hw6o/Ue8ze38U9G40FFQoSpeitnDrGoB1xvJ6siITP?= =?us-ascii?q?Z240Sv2S6X2gzN9u1JJVo4mKnbJpI737I9l5sevV7eEiLylkj6lLGaelk49uS1?= =?us-ascii?q?7unrf7brqYGfOoJxlA3zN7oil8+kDuk3NwUDXHaU9Oag2LDm/UD2WrtKjvMzn6?= =?us-ascii?q?nXrp/XJsoWq6ujDAJUzoov9xCyBCq83tsCh3kINldFdQqHj4f3P1HOJ+j1DfKl?= =?us-ascii?q?jFStlDdn3vHGPqH8DpnUIHjPjbPscLhn505Tzwozyt9f55ZKBb0bPP3zXUrxuM?= =?us-ascii?q?TZDh8/LQO03/7qBMth2o4aQ26CAa+UPLnPvVKJ5+8jOfSAaYsbtTrlLvgq/f/u?= =?us-ascii?q?jXs3mV8Heqmp2IMaaHGkEfRoO0WVe2LsgsoaHmcOvwoxUO3qiEGCUDNIaHayWK?= =?us-ascii?q?U85j4/CI24CIfMXIGtgLib0CinGZ1WY3hKCkqQHnfwa4WER/AMZTqOLcB7lzwE?= =?us-ascii?q?UaGtS4sg1RG1qA/30KFnL+rR+i0Ar53vztl15+vJlREz7zN4Fcqd03veB11zy2?= =?us-ascii?q?gBQjtz2KFkvWR8zE2C2O52ma92D9tWsshAV08GMpTdyalaDNvyQR7IcsvBHFet?= =?us-ascii?q?TM3gGSw7StM6wsMfS0l6HNqmgxXK3i7sCLgQwe/YTKco+77RiiCib/12zGzLgf?= =?us-ascii?q?F43gsWB/BXPGjjvZZRsg3aBorHiUKczvj4eqMb0yrA8W6CySyFu0QKCVcsA5WA?= =?us-ascii?q?ZmgWYw7tlfq8/lnLFuH8BrMgPQ9MzMeDLu1Bbdi71QwbFsemA8zXZieKo0n1BR?= =?us-ascii?q?uMwenSPo/jemFY3TmETUZdwltV8nGBOgwzQCympjCGAQ=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BPAABxXWRcf8GmVdFZAQMGHAEBAQQBA?= =?us-ascii?q?QcEAQGBUQcBAQsBAYEvJQWBBAxRWYNFQIgai3JPAQEHgTd6lxcUgWcLAQEjCYF?= =?us-ascii?q?Lgi+EIRoHAQQwCQ0BAwEBAgEBAQEBEwEBCQsLCBsMJQxCAQEECwGBZiKDAQ4DB?= =?us-ascii?q?h0BJQIEBgIGAxIDHAImAjYBBQEsEQELAl+BZEyBaAEDCA0BDo5gkAo8iVsagSa?= =?us-ascii?q?BL4J5BYFID4JiCkANghYCBgkBCHmLKg+BD4EHgRABgl2Bdj2BFQsCAgGBIwcJA?= =?us-ascii?q?QMBAxWDF4JXAogggUAEDRggBoYOgQZakC4PTQcChlNniG+CKhmBbVWCVIIpgwY?= =?us-ascii?q?4hFyDFo92jCcGAgkHDyGBJYIONBkjLyGCbAmCExiBCwECBoJChRSFXSEzAYEDg?= =?us-ascii?q?XmGEIQeAQENFweCIAEB?= X-IPAS-Result: =?us-ascii?q?A0BPAABxXWRcf8GmVdFZAQMGHAEBAQQBAQcEAQGBUQcBAQs?= =?us-ascii?q?BAYEvJQWBBAxRWYNFQIgai3JPAQEHgTd6lxcUgWcLAQEjCYFLgi+EIRoHAQQwC?= =?us-ascii?q?Q0BAwEBAgEBAQEBEwEBCQsLCBsMJQxCAQEECwGBZiKDAQ4DBh0BJQIEBgIGAxI?= =?us-ascii?q?DHAImAjYBBQEsEQELAl+BZEyBaAEDCA0BDo5gkAo8iVsagSaBL4J5BYFID4JiC?= =?us-ascii?q?kANghYCBgkBCHmLKg+BD4EHgRABgl2Bdj2BFQsCAgGBIwcJAQMBAxWDF4JXAog?= =?us-ascii?q?ggUAEDRggBoYOgQZakC4PTQcChlNniG+CKhmBbVWCVIIpgwY4hFyDFo92jCcGA?= =?us-ascii?q?gkHDyGBJYIONBkjLyGCbAmCExiBCwECBoJChRSFXSEzAYEDgXmGEIQeAQENFwe?= =?us-ascii?q?CIAEB?= X-IronPort-AV: E=Sophos;i="5.58,366,1544482800"; d="scan'208";a="296099304" Received: from mail-it1-f193.google.com ([209.85.166.193]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 13 Feb 2019 19:14:46 +0100 Received: by mail-it1-f193.google.com with SMTP id i2so7804055ite.5 for ; Wed, 13 Feb 2019 10:14:46 -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=5qfp2wDYmiwgEFVoRUCWNZwzT3yNWOCigCaHeI3C1Tw=; b=MFgofH7R6LmlPmCYL9Q6JmyKzYsChyvEODQKTGbeF2XeaqmD4DIqxf4FxcrYvdzF7O Jqj+1jID77oWSQrzEn4ylL+49L5n88L4M3mee7PMNvRZ+UatmlVs1Ru2pGuHtX4pQY8c SoiOZhHztuHjjchjaX93TQ4+1WahGNPLOn3O9ezutxUeNwHEQkofWiTDTw0MYVH0ljH6 zd9WYCItH99NIotrSx6F4DjOTWbCMmswOuCfIbsEO3OygNXzlOR1WBLztVhzLXOQC5bt GGzOTA2JrgXWaejFZiqtR7pqxWxyOR7so8U/w9JzvHnQPooZxmApl3EmMS4C8uAeQJgi jeVA== 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=5qfp2wDYmiwgEFVoRUCWNZwzT3yNWOCigCaHeI3C1Tw=; b=QizO9mJTEQMXURnTQjNYrV38prIOt9cY5Nl1OCy+JMJbeURJhmJDdzvvQgLYfSqEw+ GyMt2y1hQYsRQqaXPOvvR+V6+C5oITOx8WA0Q5tN/yEjXagwVTe/wmrJ3oBi5QiT53OI OjNovQyoH9H8KvQvditJYWwQKxLLHFPOC+FMEovETuDn/ULFq54qoq7hXas0lnE6PHME 5ha2IoXzr/cqT8vSxGOyLzdLuS9vPDVjaVSFUeYS/fgyP17jXUgFA02NlpBJSKKgHyM8 YJIB/SK5ElSiO4QprnofEw7AJG1Bztxh2myqoerLq+Y3DAuUSA9FIU2ZLQtU+4Ao0s/A BJtg== X-Gm-Message-State: AHQUAuaRv/Wmz8BkowGuYilpT/QTZKZ20faoG4D3KbEoJo5XT88sbeET 6Rv3p0X3H9x1++IEhMSJ9yOwKkH/ X-Google-Smtp-Source: AHgI3Ib8ILTnU9tTXvqDJcTcZ5PQMdiAg+CYdGFcrprPtNB8h7p9ig0yUCISSOwTV0vTHybSFjZhJA== X-Received: by 2002:a02:1cca:: with SMTP id c193mr1137699jac.17.1550081685017; Wed, 13 Feb 2019 10:14:45 -0800 (PST) Received: from icfp.publicity ([2001:18e8:2:28b4:8e70:5aff:fe83:a600]) by smtp.gmail.com with ESMTPSA id i135sm3628638iti.34.2019.02.13.10.14.44 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 13 Feb 2019 10:14:44 -0800 (PST) From: Sam Tobin-Hochstadt X-Google-Original-From: Sam Tobin-Hochstadt Date: Wed, 13 Feb 2019 13:14:44 -0500 To: caml-list@inria.fr Message-ID: <5c645e943280e_1b92abe6f8c25b4331e9@hermes.mail> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Caml-list] Third Call for Papers: PACMPL issue ICFP 2019 PACMPL Volume 3, Issue ICFP 2019=0D Call for Papers=0D =0D accepted papers to be invited for presentation at=0D The 24th ACM SIGPLAN International Conference on Functional Programming=0D Berlin, Germany=0D http://icfp19.sigplan.org/=0D =0D ### Important dates=0D =0D Submissions due: 1 March 2019 (Friday) Anywhere on Earth=0D https://icfp19.hotcrp.com=0D Author response: 16 April (Tuesday) - 18 Apri (Friday) 14:00 UTC=0D Notification: 3 May (Friday)=0D Final copy due: 22 June (Saturday)=0D Conference: 18 August (Sunday) - 23 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 2019 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; type=0D systems; interoperability; domain-specific languages; and=0D relations to imperative, object-oriented, or logic programming.=0D =0D * *Implementation*: abstract machines; virtual machines;=0D interpretation; compilation; compile-time and run-time=0D optimization; garbage collection and memory management;=0D multi-threading; exploiting parallel hardware; interfaces to=0D 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.=0D =0D * *Foundations*: formal semantics; lambda calculus; rewriting; type=0D theory; monads; continuations; control; state; effects; program=0D verification; dependent types.=0D =0D * *Analysis and Transformation*: control-flow; data-flow; abstract=0D interpretation; partial evaluation; program calculation.=0D =0D * *Applications*: symbolic computing; formal-methods tools;=0D artificial intelligence; systems programming; distributed-systems=0D and web programming; hardware design; databases; XML processing;=0D scientific and numerical computing; graphical user interfaces;=0D multimedia and 3D graphics 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 2019 also welcomes submissions in two separate=0D categories — Functional Pearls and Experience Reports —=0D that must be marked as such at the time of submission and that need=0D not report original research results. Detailed guidelines on both=0D categories are given at the end of this call.=0D =0D Please contact the principal editor if you have questions or are=0D concerned about the appropriateness of a topic.=0D =0D ### Preparation of submissions=0D =0D **Deadline**: The deadline for submissions is **Friday, March 1, 2019**,=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 . For authors=0D using LaTeX, a lighter-weight package, including only the essential=0D files, is available 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 14:00 UTC on **Tuesday, April 16, 2019**, 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 **Resubmitted Papers**: Authors who submit a revised version of a=0D paper that has previously been rejected by another conference have the=0D option to attach an annotated copy of the reviews of their previous=0D submission(s), explaining how they have addressed these previous=0D reviews in the present submission. If a reviewer identifies=0D him/herself as a reviewer of this previous submission and wishes to=0D see how his/her comments have been addressed, the principal editor=0D will communicate to this reviewer the annotated copy of his/her=0D previous review. Otherwise, no reviewer will read the annotated copies=0D of the previous reviews.=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 2019. 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 conference website to address=0D common concerns.=0D =0D **PACMPL issue ICFP 2019 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. At the review meeting, 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 3, 2019**.=0D =0D Authors of conditionally accepted papers will be provided with=0D committee reviews (just as in previous conferences) along with a set=0D of mandatory revisions. After four weeks (May 31, 2019), the authors=0D will provide a second submission. The second and final reviewing phase=0D assesses whether the mandatory revisions have been adequately=0D addressed by the authors and thereby determines the final=0D accept/reject status of the paper. The intent and expectation is that=0D the mandatory revisions can be addressed within four weeks and hence=0D that conditionally accepted papers will in general be accepted in the=0D 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 2019 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. It will be archived in ACM=E2=80=99= s=0D Digital Library, but no membership or fee is required for=0D access. Gold Open Access has been made possible by generous funding=0D through ACM SIGPLAN, which will cover all open access costs in the=0D event authors cannot. Authors who can cover the costs may do so by=0D paying 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 * We intend that the papers will be freely available for download from=0D the ACM Digital Library in perpetuity via the OpenTOC mechanism.=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 * At least one author of each accepted submissions will be expected to=0D attend and present their paper at the conference. The schedule for=0D presentations will be determined and shared with authors after the=0D full program has been selected. Presentations will be videotaped=0D and released online if the presenter consents.=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 ### 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 educ= ation=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 accepted Experience Report will be presented at the=0D conference, but depending on the number of Experience Reports and=0D regular papers accepted, authors of Experience reports may be=0D 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 ICFP, but it=0D 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 principal 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: Derek Dreyer (MPI-SWS, Germany)=0D =0D Artifact Evaluation Co-Chairs: Simon Marlow (Facebook, UK)=0D Industrial Relations Chair: Alan Jeffrey (Mozilla Research, USA)=0D Programming Contest Organiser: Ilya Sergey (Yale-NUS College, Singapore)=0D Publicity and Web Chair: Sam Tobin-Hochstadt (Indiana University, USA)=0D Student Research Competition Chair: William J. Bowman (University of Britis= h Columbia, Canada)=0D Workshops Co-Chair: Christophe Scholliers (Universiteit Gent, Belgium)=0D Jennifer Hackett (University of Nottingham, UK)=0D Conference Manager: Annabel Satin (P.C.K.) =0D =0D =0D ### PACMPL Volume 3, Issue ICFP 2019=0D =0D Principal Editor: Fran=C3=A7ois Pottier (Inria, France)=0D =0D Review Committee:=0D =0D Lennart Beringer (Princeton University, United States)=0D Joachim Breitner (DFINITY Foundation, Germany)=0D Laura M. Castro (University of A Coru=C3=B1a, Spain)=0D Ezgi =C3=87i=C3=A7ek (Facebook London, United Kingdom)=0D Pierre-Evariste Dagand (LIP6/CNRS, France)=0D Christos Dimoulas (Northwestern University, United States)=0D Jacques-Henri Jourdan (CNRS, LRI, Universit=C3=A9 Paris-Sud, France)=0D Andrew Kennedy (Facebook London, United Kingdom)=0D Daan Leijen (Microsoft Research, United States)=0D Kazutaka Matsuda (Tohoku University, Japan)=0D Bruno C. d. S. Oliveira (University of Hong Kong, China)=0D Klaus Ostermann (University of T=C3=BCbingen, Germany)=0D Jennifer Paykin (Galois, United States)=0D Frank Pfenning (Carnegie Mellon University, USA)=0D Mike Rainey (Indiana University, USA)=0D Chung-chieh Shan (Indiana University, USA)=0D Sam Staton (University of Oxford, UK)=0D Pierre-Yves Strub (Ecole Polytechnique, France)=0D German Vidal (Universitat Politecnica de Valencia, Spain)=0D =0D External Review Committee:=0D =0D Michael D. Adams (University of Utah, USA)=0D Robert Atkey (University of Strathclyde, IK)=0D Sheng Chen (University of Louisiana at Lafayette, USA)=0D James Cheney (University of Edinburgh, UK)=0D Adam Chlipala (Massachusetts Institute of Technology, USA)=0D Evelyne Contejean (LRI, Universit=C3=A9 Paris-Sud, France) =0D Germ=C3=A1n Andr=C3=A9s Delbianco (IRIF, Universit=C3=A9 Paris Diderot, Fr= ance)=0D Dominique Devriese (Vrije Universiteit Brussel, Belgium)=0D Richard A. Eisenberg (Bryn Mawr College, USA)=0D Conal Elliott (Target, USA)=0D Sebastian Erdweg (Delft University of Technology, Netherlands)=0D Michael Greenberg (Pomona College, USA)=0D Adrien Guatto (IRIF, Universit=C3=A9 Paris Diderot, France)=0D Jennifer Hackett (University of Nottingham, UK)=0D Troels Henriksen (University of Copenhagen, Denmark)=0D Chung-Kil Hur (Seoul National University, Republic of Korea)=0D Roberto Ierusalimschy (PUC-Rio, Brazil)=0D Ranjit Jhala (University of California, San Diego, USA)=0D Ralf Jung (MPI-SWS, Germany)=0D Ohad Kammar (University of Oxford, UK)=0D Oleg Kiselyov (Tohoku University, Japan)=0D Hsiang-Shang =E2=80=98Josh=E2=80=99 Ko (National Institute of Informatics,= Japan)=0D Ond=C5=99ej Lhot=C3=A1k (University of Waterloo, Canada)=0D Dan Licata (Wesleyan University, USA)=0D Geoffrey Mainland (Drexel University, USA)=0D Simon Marlow (Facebook, UK)=0D Akimasa Morihata (University of Tokyo, Japan)=0D Shin-Cheng Mu (Academia Sinica, Taiwan)=0D Guillaume Munch-Maccagnoni (Inria, France)=0D Kim Nguy=E1=BB=85n (University of Paris-Sud, France)=0D Ulf Norell (Gothenburg University, Sweden)=0D Atsushi Ohori (Tohoku University, Japan)=0D Rex Page (University of Oklahoma, USA)=0D Zoe Paraskevopoulou (Princeton University, USA)=0D Nadia Polikarpova (University of California, San Diego, USA)=0D Jonathan Protzenko (Microsoft Research, USA)=0D Tiark Rompf (Purdue University, USA)=0D Andreas Rossberg (Dfinity, Germany)=0D KC Sivaramakrishnan (University of Cambridge, UI)=0D Nicholas Smallbone (Chalmers University of Technology, Sweden)=0D Matthieu Sozeau (Inria, France)=0D Sandro Stucki (Chalmers | University of Gothenburg, Sweden)=0D Don Syme (Microsoft, UK)=0D Zachary Tatlock (University of Washington, USA)=0D Sam Tobin-Hochstadt (Indiana University, USA)=0D Takeshi Tsukada (University of Tokyo, Japan)=0D Tarmo Uustalu (Reykjavik University, Iceland)=0D Benoit Valiron (LRI, CentraleSupelec, Univ. Paris Saclay, France)=0D Daniel Winograd-Cort (University of Pennsylvania, USA)=0D Nicolas Wu (University of Bristol, UK)=