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 sympa.inria.fr (Postfix) with ESMTPS id 76FC1824E4 for ; Fri, 9 Nov 2018 03:44:42 +0100 (CET) Authentication-Results: mail2-smtp-roc.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-f175.google.com Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of icfp.publicity@googlemail.com) identity=pra; client-ip=209.85.166.175; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="icfp.publicity@googlemail.com"; x-sender="icfp.publicity@googlemail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of icfp.publicity@googlemail.com designates 209.85.166.175 as permitted sender) identity=mailfrom; client-ip=209.85.166.175; receiver=mail2-smtp-roc.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 (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-it1-f175.google.com) identity=helo; client-ip=209.85.166.175; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="icfp.publicity@googlemail.com"; x-sender="postmaster@mail-it1-f175.google.com"; x-conformance=sidf_compatible IronPort-PHdr: =?us-ascii?q?9a23=3AeeGmvBMjaiiFojgCQKcl6mtUPXoX/o7sNwtQ0KIM?= =?us-ascii?q?zox0I/3zrarrMEGX3/hxlliBBdydt6obzbKO+4nbGkU4qa6bt34DdJEeHzQksu?= =?us-ascii?q?4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1?= =?us-ascii?q?Ov71GonPhMiryuy+4ZLebxlKiTanfb9+MAi9oBnMuMURnYZsMLs6xAHTontPde?= =?us-ascii?q?RWxGdoKkyWkh3h+Mq+/4Nt/jpJtf45+MFOTav1f6IjTbxFFzsmKHw65NfqtRbY?= =?us-ascii?q?UwSC4GYXX3gMnRpJBwjF6wz6Xov0vyDnuOdxxDWWMMvrRr0yRD+s7bpkSAXwhS?= =?us-ascii?q?kHOTA37mLZhNF/g61HrxysvAB/w5fObY2JKPZyYqHQcNUHTmRBRMZRUClBD5uh?= =?us-ascii?q?YYQVCuoKIPhWr47mqFsPqxuyHAuiBOTzxT9InX/2wbc13Pk9EQrb2wEgHs4BsH?= =?us-ascii?q?rMrNnvLKcSTPu6zK3JzTrfbvNWxTf85ZPHchAmpvGMUrZwftTUyUY1FgPFik+c?= =?us-ascii?q?ppDiPzOQz+kAtXWQ4eRnVeKqkWEnqgdxryC1ycgwj4nFnIUVykrL9Slh24Y1JN?= =?us-ascii?q?K4SFZ/YdG+FptcrSaaN5F5Qs86TWBouSU6yrweuZGlYScKyY4oywTYa/ydfIiE?= =?us-ascii?q?+hLjVOGNIThknnJlYKiziAq18Uil0uH8UdO70E1SriVfiNXMsWoN1xPV58OaSf?= =?us-ascii?q?V95l+s1SiT2w3X8O1JIkA5mbDGJ5Mgw7M8jIcfvEbDEyPumUj7j7Wae0ok9+Sy?= =?us-ascii?q?6enrfK/qqoKTOoNojAz1L74gldalAesiNwgDR2ib9vq41L3k5UD5Ra9Fjvwykq?= =?us-ascii?q?XAsZDaOdkXqre3AwNI0Isu6wyzDzih0NQfknkHKExKdAibgIjuPlHCOPH4DfGh?= =?us-ascii?q?jFSwiDpn2ezKM7n7DpjOLnXPiqrtcLd85kJG1QY+z9BS64pRCr4bIfLzXkHxtM?= =?us-ascii?q?bfDh88KwG0wvroCNtl1o8EQWKPH7SWMKfTsVCU5+IvP+mNaZQauDb6LPgl6Pru?= =?us-ascii?q?gmE8mVAHfKmp2YEbZ2y/HvRjO0mZe2bjgs8dEWcWuQozVPDlh0eHUT5XfnqyW6?= =?us-ascii?q?M85ionCI+9FofCRoWtgKSb0yuhH51WYHpGClGWHnvyeYWEQaREVCXHKcZklnkA?= =?us-ascii?q?VKO9Y44nzxCn8gHgmJR9Ke+BwSQd/a7k3tlzos3UnhEp6TV4E4zJ0mqDVydsg2?= =?us-ascii?q?kMRjQ3wLFXrkt6xVOO1KF5h7pTEtkFtKABaRszKZOJl78yMNv1QA+UJo7YGmbj?= =?us-ascii?q?ec2vBHQKdvx0xtYPZ0hnHND70ELM2C2lB7IQnr2PQpcz9/CFhiSjF4NG03/DkZ?= =?us-ascii?q?IZoRw+WMIWaz+pgalw8wXWDo/N1U6ekvTyLPlO7Gv27G6GiFG2kgRYXQp3C/uX?= =?us-ascii?q?WHkeYg7XsY286BqdEvmhDrMoNgYHwsmHePNH?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B9AAAZ9ORbf6+mVdFaAQMGHAEBAQQBA?= =?us-ascii?q?QcEAQGBUQcBAQsBAYFUBYEDDIEpgzk/iBhfixxPAQEHgTd4ljgUgWYLAQEFHgm?= =?us-ascii?q?BS4Ivg2AaBwEEMA0NAQMBAQIBAQEBARMBAQkLCwgbDCUMQhYBgV0ignUOAwYdA?= =?us-ascii?q?SUCBAYCBgMSAxwCJgI2AQUBLBILAl+BYUyBaAEDCA0PjEqQBzyJWRGBI4Eugnc?= =?us-ascii?q?FgUYPgmQKQA2CEQIGCQEIeYpfD4EQgQeBEAGCXYF2PYESCwICAYEjBwkBAwEDF?= =?us-ascii?q?YMSglcCh0SBKgQNFiAGhUd2To4tD0YHAoYSYId/giUYgVdMgi+CBoJsCyuECIJ?= =?us-ascii?q?qjSCKKQIEAgQFAgUPIYEigg00GSMvIYJsCYISGIEKAQIGgkKFFIVcITMBgQOHe?= =?us-ascii?q?IIHAQENFweCIAEB?= X-IPAS-Result: =?us-ascii?q?A0B9AAAZ9ORbf6+mVdFaAQMGHAEBAQQBAQcEAQGBUQcBAQs?= =?us-ascii?q?BAYFUBYEDDIEpgzk/iBhfixxPAQEHgTd4ljgUgWYLAQEFHgmBS4Ivg2AaBwEEM?= =?us-ascii?q?A0NAQMBAQIBAQEBARMBAQkLCwgbDCUMQhYBgV0ignUOAwYdASUCBAYCBgMSAxw?= =?us-ascii?q?CJgI2AQUBLBILAl+BYUyBaAEDCA0PjEqQBzyJWRGBI4EugncFgUYPgmQKQA2CE?= =?us-ascii?q?QIGCQEIeYpfD4EQgQeBEAGCXYF2PYESCwICAYEjBwkBAwEDFYMSglcCh0SBKgQ?= =?us-ascii?q?NFiAGhUd2To4tD0YHAoYSYId/giUYgVdMgi+CBoJsCyuECIJqjSCKKQIEAgQFA?= =?us-ascii?q?gUPIYEigg00GSMvIYJsCYISGIEKAQIGgkKFFIVcITMBgQOHeIIHAQENFweCIAE?= =?us-ascii?q?B?= X-IronPort-AV: E=Sophos;i="5.54,481,1534802400"; d="scan'208";a="354848968" Received: from mail-it1-f175.google.com ([209.85.166.175]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 09 Nov 2018 03:44:40 +0100 Received: by mail-it1-f175.google.com with SMTP id e11so1203205itl.5 for ; Thu, 08 Nov 2018 18:44:40 -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=hUIREn4q4FOyZAiet7q1Rmct2X5JM2ZxulISisuoGdM=; b=QEEB3Wfk/07W2+d77wIOHrHWeHlwlI/qM1hGaxGgPy3/6yH5FHMpp2e/t4xB1lWeYz zcu/I2hWGkveYvbm5jXvDKpPRzUOq3AU+RrVT7tHEHn9kv6AQppMLlh3T5gE1VCKxzCd wnBy4qOKE+udFGOw6u4tSKZb1Ne/9EH9VZRtgBbqn1vC3M8MnN6nOY/0PW8oFAEcwKDg ICvOxC9tRcebRKTvRQBskLS0SUs0ORGTsS5U1LOXZeuFo1h0XAJDUUSOcggh2bpW+ft/ fHZ/HmdbyZrx46RZaWnH2siU14UvOOCAdZONwI1mZKk13Tepb5pGXRT2cJXmldKwD71p opAw== 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=hUIREn4q4FOyZAiet7q1Rmct2X5JM2ZxulISisuoGdM=; b=WJIqs3HXVF7QO7+rArO0ImbN0/xV66gptsQum8OfIZazLHRLczUV5nnyksXY1rSEgG 1tG0enIyTUjRCXhSo5yBfzSeYMnjbqLtiQOR6j2vpRTes3hbJI+OKBag8u841XgDBGVz SHq7YH3p6DqmMBQEtyHivRpW3QWz5r0iceGmkkO96MQnCUUYZRNYcFAi06sYSBTiGZZu Zae6Fq57hn5hvA9NmEV8BD8y8z2xEyohXbNxAsRT7uNLBcmue5rJmdd1fn4rtNiN4rLk tG7LzLVNzU7ezv97kd/58FYcXmLs/+HbQMzSzzzoKpldO0/sUW1MWUi8s+Fl7nIwqXUX RX4A== X-Gm-Message-State: AGRZ1gI900Lbsn2mpbZlWgH13yu+WzJnGCCATQQT7UkvdmY4JL/qyQC/ QgBSuy5oDHIJZFy3m7XKdDTegE52gu8= X-Google-Smtp-Source: AJdET5c6AKm0dby8Buk1AFdQeNjd6ONoz8wDRw/fUY+Ub2j1BVhKdrXOZETFGTjTeg03vR2X6I3D9Q== X-Received: by 2002:a05:660c:40e:: with SMTP id c14mr772357itk.119.1541731478142; Thu, 08 Nov 2018 18:44:38 -0800 (PST) Received: from icfp.publicity (c-68-45-72-140.hsd1.de.comcast.net. [68.45.72.140]) by smtp.gmail.com with ESMTPSA id k17-v6sm136748itk.9.2018.11.08.18.44.36 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Nov 2018 18:44:37 -0800 (PST) From: Sam Tobin-Hochstadt X-Google-Original-From: Sam Tobin-Hochstadt Date: Thu, 08 Nov 2018 21:44:36 -0500 To: caml-list@inria.fr Message-ID: <5be4f494edb8e_1c8812990cc3824b@hermes.mail> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Caml-list] First 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 ) 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 publicized Calls for Papers, like this one.=0D =0D ### Scope=0D =0D [PACMPL](https://pacmpl.acm.org/) issue ICFP 2019 seeks original papers on = the art and science of functional programming. Submissions are invited on a= ll topics from principles to practice, from foundations to features, and fr= om abstraction to application. The scope includes all languages that encour= age functional programming, including both purely applicative and imperativ= e languages, as well as languages with objects, concurrency, or parallelism= . Topics of interest include (but are not limited to):=0D =0D * *Language Design*: concurrency, parallelism, and distribution; modules;= components and composition; metaprogramming; type systems; interoperabilit= y; domain-specific languages; and relations to imperative, object-oriented,= or logic programming.=0D =0D * *Implementation*: abstract machines; virtual machines; interpretation; = compilation; compile-time and run-time optimization; garbage collection and= memory management; multi-threading; exploiting parallel hardware; interfac= es to foreign functions, services, components, or low-level machine resourc= es.=0D =0D * *Software-Development Techniques*: algorithms and data structures; desi= gn patterns; specification; verification; validation; proof assistants; deb= ugging; testing; tracing; profiling.=0D =0D * *Foundations*: formal semantics; lambda calculus; rewriting; type theor= y; monads; continuations; control; state; effects; program verification; de= pendent types.=0D =0D * *Analysis and Transformation*: control-flow; data-flow; abstract interp= retation; partial evaluation; program calculation.=0D =0D * *Applications*: symbolic computing; formal-methods tools; artificial in= telligence; systems programming; distributed-systems and web programming; h= ardware design; databases; XML processing; scientific and numerical computi= ng; graphical user interfaces; multimedia and 3D graphics programming; scri= pting; system administration; security.=0D =0D * *Education*: teaching introductory programming; parallel programming; m= athematical proof; algebra.=0D =0D Submissions will be evaluated according to their relevance, correctness, si= gnificance, originality, and clarity. Each submission should explain its co= ntributions in both general and technical terms, clearly identifying what h= as been accomplished, explaining why it is significant, and comparing it wi= th previous work. The technical content should be accessible to a broad aud= ience.=0D =0D PACMPL issue ICFP 2019 also welcomes submissions in two separate categories= — Functional Pearls and Experience Reports — that must be mark= ed as such at the time of submission and that need not report original rese= arch results. Detailed guidelines on both categories are given at the end = of this call.=0D =0D Please contact the principal editor if you have questions or are concerned = about the appropriateness of a topic.=0D =0D ### Preparation of submissions=0D =0D **Deadline**: The deadline for submissions is **Friday, March 1, 2019**, An= ywhere on Earth (). This = deadline will be strictly enforced.=0D =0D **Formatting**: Submissions must be in PDF format, printable in black and w= hite on US Letter sized paper, and interpretable by common PDF tools. All s= ubmissions must adhere to the "ACM Small" template that is available (in bo= th LaTeX and Word formats) from . For authors using LaTeX, a lighter-weight package, including = only the essential files, is available from .=0D =0D 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 will= not be counted against these limits. Submissions that exceed the page limi= ts or, for other reasons, do not meet the requirements for formatting, will= be summarily rejected. Supplementary material can and should be **separate= ly** submitted (see below).=0D =0D See also PACMPL's Information and Guidelines for Authors at .=0D =0D **Submission**: Submissions will be accepted at =0D =0D Improved versions of a paper may be submitted at any point before the submi= ssion deadline using the same web interface.=0D =0D **Author Response Period**: Authors will have a 72-hour period, starting at= 14:00 UTC on **Tuesday, April 16, 2019**, to read reviews and respond to t= hem.=0D =0D **Supplementary Material**: Authors have the option to attach supplementary= =0D material to a submission, on the understanding that reviewers may choose no= t=0D to look at it. This supplementary material should **not** be submitted as p= art=0D of the main document; instead, it should be uploaded as a **separate** PDF= =0D document or tarball.=0D =0D Supplementary material should be uploaded **at submission time**, not by=0D providing a URL in the paper that points to an external repository.=0D =0D Authors are free to upload both anonymized and non-anonymized supplementary= =0D material. Anonymized supplementary material will be visible to reviewers=0D immediately; non-anonymized supplementary material will be revealed to=0D reviewers only after they have submitted their review of the paper and lear= ned=0D the identity of the author(s).=0D =0D **Authorship Policies**: All submissions are expected to comply with the AC= M Policies for Authorship that are detailed at .=0D =0D **Republication Policies**: Each submission must adhere to SIGPLAN's republ= ication policy, as explained on the web at .=0D =0D **Resubmitted Papers**: Authors who submit a revised version of a paper tha= t has previously been rejected by another conference have the option to att= ach an annotated copy of the reviews of their previous submission(s), expla= ining how they have addressed these previous reviews in the present submiss= ion. If a reviewer identifies him/herself as a reviewer of this previous su= bmission and wishes to see how his/her comments have been addressed, the pr= incipal editor will communicate to this reviewer the annotated copy of his/= her previous review. Otherwise, no reviewer will read the annotated copies = of the previous reviews.=0D =0D ### Review Process=0D =0D This section outlines the two-stage process with lightweight double-blind r= eviewing that will be used to select papers for PACMPL issue ICFP 2019. We= anticipate that there will be a need to clarify and expand on this process= , and we will maintain a list of frequently asked questions and answers on = the conference website to address common concerns.=0D =0D **PACMPL issue ICFP 2019 will employ a two-stage review process.** The fir= st stage in the review process will assess submitted papers using the crite= ria stated above and will allow for feedback and input on initial reviews t= hrough the author response period mentioned previously. At the review meeti= ng, a set of papers will be conditionally accepted and all other papers wil= l be rejected. Authors will be notified of these decisions on **May 3, 201= 9**.=0D =0D Authors of conditionally accepted papers will be provided with committee re= views (just as in previous conferences) along with a set of mandatory revis= ions. After four weeks (May 31, 2019), the authors will provide a second su= bmission. The second and final reviewing phase assesses whether the mandato= ry revisions have been adequately addressed by the authors and thereby dete= rmines the final accept/reject status of the paper. The intent and expectat= ion is that the mandatory revisions can be addressed within four weeks and = hence that conditionally accepted papers will in general be accepted in the= second phase.=0D =0D The second submission should clearly identify how the mandatory revisions w= ere addressed. To that end, the second submission must be accompanied by a = cover letter mapping each mandatory revision request to specific parts of t= he paper. The cover letter will facilitate a quick second review, allowing = for confirmation of final acceptance within two weeks. Conversely, the abse= nce of a cover letter will be grounds for the paper=E2=80=99s rejection.=0D =0D **PACMPL issue ICFP 2019 will employ a lightweight double-blind reviewing p= rocess.** To facilitate this, submitted papers must 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 perso= n** (e.g., not "We build on our previous work ..." but rather "We build on = the work of ...").=0D =0D The purpose of this process is to help the reviewers come to an initial jud= gement about the paper without bias, not to make it impossible for them to = discover the authors if they were to try. Nothing should be done in the nam= e of anonymity that weakens the submission or makes the job of reviewing th= e paper more difficult (e.g., important background references should not be= omitted or anonymized). In addition, authors should feel free to dissemina= te their ideas or draft versions of their paper as they normally would. For= instance, authors may post drafts of their papers on the web or give talks= on their research ideas.=0D =0D ### Information for Authors of Accepted Papers=0D =0D * As a condition of acceptance, final versions of all papers must adhere to= the new 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**.= =0D =0D * Authors of accepted submissions will be required to agree to one of the t= hree ACM licensing options: open access on payment of a fee (**recommended*= *, and SIGPLAN can cover the cost as described next); copyright transfer to= ACM; or retaining copyright but granting ACM exclusive publication rights.= Further information about ACM author rights is available from .=0D =0D * PACMPL is a Gold Open Access journal. It will be archived in ACM=E2=80=99= s Digital Library, but no membership or fee is required for access. Gold Op= en Access has been made possible by generous funding through ACM SIGPLAN, w= hich 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 (A= PC). PACMPL, SIGPLAN, and ACM Headquarters are committed to exploring route= s to making Gold Open Access publication both affordable and sustainable.=0D =0D * ACM offers authors a range of copyright options, one of which is Creative= Commons CC-BY publication; this is the option recommended by the PACMPL ed= itorial board. A reasoned argument in favour of this option can be found in= the article [Why CC-BY?](https://oaspa.org/why-cc-by/) published by OASPA,= the Open Access Scholarly Publishers Association.=0D =0D * We intend that the papers will be freely available for download from the = ACM Digital Library in perpetuity via the OpenTOC mechanism.=0D =0D * 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 vi= sitors to download the definitive version of their articles from the ACM Di= gital Library at no charge. Downloads through Author-Izer links are capture= d in official ACM statistics, improving the accuracy of usage and impact me= asurements. Consistently linking to the definitive version of an ACM articl= e should reduce user confusion over article versioning. After an article ha= s been published and assigned to the appropriate ACM Author Profile pages, = authors should visit to learn 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 atte= nd and present their paper at the conference. The schedule for presentatio= ns will be determined and shared with authors after the full program has be= en selected. Presentations will be videotaped and released online if the p= resenter consents.=0D =0D * The official publication date is the date the papers are made available i= n the ACM Digital Library. This date may be up to *two weeks prior* to the = first day of the conference. The official publication date affects the dead= line for any patent filings related to published work.=0D =0D ### Artifact Evaluation=0D =0D 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, wh= ose task is to assess how the artifacts support the work described in the a= ssociated paper. Papers that go through the Artifact Evaluation process suc= cessfully will receive a seal of approval printed on the papers themselves.= Authors of accepted papers will be encouraged to make the supporting mater= ials publicly available upon publication of the papers, for example, by inc= luding them as "source materials" in the ACM Digital Library. An additiona= l seal will mark papers whose artifacts are made available, as outlined in = the ACM guidelines for artifact badging.=0D =0D Participation in Artifact Evaluation is voluntary and will not influence th= e final decision regarding paper acceptance.=0D =0D ### Special categories of papers=0D =0D In addition to research papers, PACMPL issue ICFP solicits two kinds of pap= ers that do not require original research contributions: Functional Pearls,= which are full papers, and Experience Reports, which are limited to half t= he length of a full paper. Authors submitting such papers should consider t= he following guidelines.=0D =0D #### Functional Pearls=0D =0D A Functional Pearl is an elegant essay about something related to functiona= l 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 short p= rogram, there is no requirement or expectation that they do so. Thus, they = encompass the notions of theoretical and educational pearls.=0D =0D Functional Pearls are valued as highly and judged as rigorously as ordinary= papers, but using somewhat different criteria. In particular, a pearl is n= ot required to report original research, but, it should be concise, instruc= tive, and entertaining. A pearl is likely to be rejected if its readers get= bored, if the material gets too complicated, if too much specialized knowl= edge is needed, or if the writing is inelegant. The key to writing a good p= earl is polishing.=0D =0D A submission that is intended to be treated as a pearl must be marked as su= ch on the submission web page, and should contain the words "Functional Pea= rl" somewhere in its title or subtitle. These steps will alert reviewers to= use the appropriate evaluation criteria. Pearls will be combined with ordi= nary papers, however, for the purpose of computing the conference's accepta= nce rate.=0D =0D =0D #### Experience Reports=0D =0D The purpose of an Experience Report is to help create a body of published, = refereed, citable evidence that functional programming really works —= or to describe what obstacles prevent it from 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 in t= he context of an industrial project or a university curriculum=0D =0D * project-management, business, or legal issues encountered when using fu= nctional 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 implement= ation of a functional language or for functional programming in general=0D =0D 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.=0D =0D * Both in the papers and in any citations, the title of each accepted Exp= erience Report must end with the words "(Experience Report)" in parentheses= . The acceptance rate for Experience Reports will be computed and reported = separately from the rate for ordinary papers.=0D =0D * Experience Report submissions can be at most 12 pages long, excluding b= ibliography.=0D =0D * Each accepted Experience Report will be presented at the conference, bu= t depending on the number of Experience Reports and regular papers accepted= , authors of Experience reports may be asked to give shorter talks.=0D =0D * Because the purpose of Experience Reports is to enable our community to= accumulate a body of evidence about the efficacy 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 conclus= ions. It is sufficient if the Report states a clear thesis and provides sup= porting evidence. The thesis must be relevant to ICFP, but it need not be n= ovel.=0D =0D The review committee will accept or reject Experience Reports based on whet= her they judge the evidence to be convincing. Anecdotal evidence will be ac= ceptable provided it is well argued and the author explains what efforts we= re made to gather as much evidence as possible. Typically, more convincing = evidence is obtained from papers which show how functional programming was = used than from papers which only say that functional programming was used. = The most convincing evidence often includes comparisons of situations befor= e and after the introduction or discontinuation of functional programming. = Evidence drawn from a single person's experience may be sufficient, but mor= e weight will be given to evidence drawn from the experience of groups of p= eople.=0D =0D An Experience Report should be short and to the point: it should make a cla= im about how well functional programming worked on a particular project and= why, and produce evidence to substantiate this claim. If functional progra= mming worked in this case in the same ways it has worked for others, the pa= per need only summarize the results — the main part of the paper shou= ld discuss how well it worked and in what context. Most readers will not wa= nt to know all the details of the project and its implementation, but the p= aper should characterize the project and its context well enough so that re= aders can judge to what degree this experience is relevant to their own pro= jects. The paper should take care to highlight any unusual aspects of the p= roject. Specifics about the project are more valuable than generalities abo= ut functional programming; for example, it is more valuable to say that the= team delivered its software a month ahead of schedule than it is to say th= at functional programming made the team more productive.=0D =0D If the paper not only describes experience but also presents new technical = results, or if the experience refutes cherished beliefs of the functional-p= rogramming 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 principal editor will be happy to 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)=