From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=192.134.164.83; helo=mail2-relais-roc.national.inria.fr; envelope-from=caml-list-owner@inria.fr; receiver= Authentication-Results: plum; dmarc=fail (p=quarantine dis=none) header.from=googlemail.com Authentication-Results: plum.tunbury.org; dkim=pass (1024-bit key; unprotected) header.d=inria.fr header.i=@inria.fr header.a=rsa-sha256 header.s=dc header.b=JmFsipB+; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=googlemail.com header.i=@googlemail.com header.a=rsa-sha256 header.s=20230601 header.b=JIkTn2K2; dkim-atps=neutral Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by plum.tunbury.org (Postfix) with ESMTPS id 0E0ECB80123 for ; Mon, 4 Nov 2024 16:35:55 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=mime-version:from:date:message-id:to:subject:reply-to: sender:list-id:list-help:list-subscribe:list-unsubscribe: list-post:list-owner:list-archive; bh=ZfczDQYVMMTKcmxtmRdJREEnsWo+JIkDkgMmU4FYaXQ=; b=JmFsipB+wjPOtFutaUtawrMnoZ31UeQqBysuD7Z/bJVizpSbFeXdITNH juMsBU38D1MtAUVFeS+TrBE39BSmfnKz44AqRLdycg7Mv2vGhbdEZvDFP kqeRqEU1995Nqr3ICQv9z710MaS0wY4eqtvFG29YfKKCf62ySz2jnft8L s=; Received-SPF: Pass (mail2-relais-roc.national.inria.fr: domain of caml-list-owner@inria.fr designates 128.93.162.160 as permitted sender) identity=mailfrom; client-ip=128.93.162.160; receiver=mail2-relais-roc.national.inria.fr; envelope-from="caml-list-owner@inria.fr"; x-sender="caml-list-owner@inria.fr"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 include:mailout.safebrands.com a:basic-mail.safebrands.com a:basic-mail01.safebrands.com a:basic-mail02.safebrands.com ip4:128.93.142.0/24 ip4:192.134.164.0/24 ip4:128.93.162.160 ip4:128.93.162.3 ip4:128.93.162.88 ip4:89.107.174.7 mx ~all" Received-SPF: None (mail2-relais-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@sympa.inria.fr) identity=helo; client-ip=128.93.162.160; receiver=mail2-relais-roc.national.inria.fr; envelope-from="caml-list-owner@inria.fr"; x-sender="postmaster@sympa.inria.fr"; x-conformance=spf_only Authentication-Results: mail2-relais-roc.national.inria.fr; spf=Pass smtp.mailfrom=caml-list-owner@inria.fr; spf=None smtp.helo=postmaster@sympa.inria.fr; dkim=hardfail (signature did not verify [final]) header.i=@googlemail.com X-IronPort-AV: E=Sophos;i="6.11,257,1725314400"; d="scan'208,217";a="192095882" Received: from prod-listesu18.inria.fr (HELO sympa.inria.fr) ([128.93.162.160]) by mail2-relais-roc.national.inria.fr with ESMTP; 04 Nov 2024 17:35:55 +0100 Received: by sympa.inria.fr (Postfix, from userid 20132) id E9A43E0D21; Mon, 4 Nov 2024 17:35:54 +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 C9099E00B7 for ; Mon, 4 Nov 2024 17:35:49 +0100 (CET) IronPort-SDR: 6728f7e3_yfERH+XzOvF+w3PgKe5CcMxyllZh5P2Kzta/2lNeLocMKtu Ha2ers+cl7sA0s6+yl0A1hoVMgz6Ov3U9l2Jwww== X-IPAS-Result: =?us-ascii?q?A0G1AwCE9yhngTKmVdFQAQMGhB1bKH1ZNAQLSIRWgSOCH?= =?us-ascii?q?Q9TiyuBfwUdgRaBL48GiTKDL4EsFigPAQMBDTsJBAEBAwEDggyCLkaKNAIeB?= =?us-ascii?q?wEENBMBAgQBAQEBAwIDAQEBAQEBEAEBBQEBAQIBAQIEBgECEAEBIhkHDjuFQ?= =?us-ascii?q?QgyCwKCRRo3cV5HAQEBAQEBAQEBAQEBAQEBAQEBAQEBARQCDQcYBA0uFyEIA?= =?us-ascii?q?QIGHQEkAwMBAgQCBgMSEAUoAQkCIxIBBQEoAQMRAQsCDDgagTVZgi8BAzEDE?= =?us-ascii?q?aAEgiSBBUKJcho3eoEygQGCDQaBCT4FEA/YcQpBDWyBYwIHFIE0hHN3gmIBg?= =?us-ascii?q?VwCDoN9g316FxAPgVVEgRQBNYI9doEFPYEUCwQCgR8HCQEDARg9gy4WglMEg?= =?us-ascii?q?TtrIS87EkExA4FmAVFkEiMCDEs8AgEBAgcChCgBT4FugQ1bgyaDPGmBTytdg?= =?us-ascii?q?SWBTnqIMCMDJgMHBw4rSQ4BIQMmMzIBVRMXCwcFMlgKA2IBAgE2CQgDBAJCC?= =?us-ascii?q?QU3CAsLCwgTCwMGCQReBy0CAgQDBSQHBgMPUAQKAgIDAxkCBRY2AwMGBToFF?= =?us-ascii?q?RADAgYFAwIiBQIDAy4HBS8KHwOBCQgGDBRKAgUHGgsyNwMKQwMTBQUeBwOBN?= =?us-ascii?q?0cmBQYZAwQDAxIBAjcMBg4rBwMGAwMHHAUCAwMIUwMGDUoMNgc2BAgDAxcKK?= =?us-ascii?q?gICAwMZNQMCBQMFAgYKCgMDAxUaBgICBQtkCAkDAyIEFgYFHw8WCQMWDxoKA?= =?us-ascii?q?wMDCRQDGBwIBQUwEwMFAzUDAwMEEgMjAgMOGCAFEwM6EgMGCkFQCA0CAgorC?= =?us-ascii?q?QmBXgctFAcDIAMbNQUmHQMGDBEDAxkEEQIkAwYEA04CCCYDAgIDHQwIHQMIB?= =?us-ascii?q?CIrFQ4KDy8DAwMDgRgDBTwDKFQDEgVJBkwdQAMLYgs9NS9MnVNpR4I1CQgKE?= =?us-ascii?q?j8HBxATByYJAwQDCB8ICQgPARMNAi0zAwcEAQcFEgEEDgsDAQkFBgMDGAEFC?= =?us-ascii?q?gEBARYFBgMBAgsvklAQFAEmjzyCIIE0ijyTUYEKNAcrg3KBYwyKJ5VDM4FPg?= =?us-ascii?q?jWNAYcAiwWGXGWkFYE3gSmHVI1PLgIchSMRI4FbI4FcNBkjL1JtCYFACQk9A?= =?us-ascii?q?xkPV4g/hSKBFwEIgkOFFL8KKDICOQIHAQoBAQMJjnYBAQ8XBwWBSwEB?= IronPort-PHdr: A9a23:WCR4qhWwdpm03GNssNT0NfoY7RHV8KwrXDF92vMcY1JmTK2v8tzYM VDF4r011RmVBt2dsaMawLqG+4nbGkU+or+580o+OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF 95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjWwbL1uI BmsswncssgbjYRhJ6sy1xDEvmZGd+NKyGxnIl6egwzy6sCs8pB97i9eoegh98lOUaX7e6Q3U 7lVByk4Pm42+cPmqwDNQROA6XUAXGoWlAFIAxXe4xHhQpjxqCr6ufFj1yScIMb7UKo7WTWm7 6dsVR/olCIKPCM3/W3LlsB9ir9QrxW8pxx53oHUYZqVO+Z6fqPaZtMVW3dOVdtVWyFOHo+wa o0CBPcDM+lFtYnwv1QBoxuwCwevGe3g1iJFi2Ts0qEmyeksCx3K0BAiEt8IrX/arM/1NKAXU e2tz6fF0zXNYelL0jnn9YjHaRQhofCQUrJxbcrQyVQkGgTEjlqMp4zlJymZ1vwQs2eA6+pgV P6gi287qwBxuTWvycAsio7GhoIR1F/E8D92wIcxJdGiVEF7ZtukHYJWuiqHOIR4XtksTHt0u CYm1LIGo5i7cTAXxZkoxxPRZPyKfpWU7h7+SOqcPzh1iXFrdr+hmxu/80itx+PiWse0zlpGs zZJnsXMu30QyRHe69WLR/Ry8Eu/3zuEyg7d6uZBIU8ulKrbLYYswqUxlpocqUTDGjX5mEPsg K+RbEUk9fCk6/75bbX9uJCTLZV0hR3+MqQ0gMC/Bv44MgcWU2iH+OS80aPs8lf/QLpXk/I5i LXZv47AKcsHoa65BhdZ3Zw/5Ba6FTum184YnXYfIFJFfxKHk5TmO0vWIPziEfi/hFGsnC9sx /DcIrLhA4jCImLEkLf7crZw7VNXxgkrzd1H+Z5YFrUMLOjwV0LxrtDUEx40Pg2uz+vnFNlw0 J4VVHyLAq+EK6PSrUGH5vgyLemNZY4api7wJ+Qj6vXzl3E2g0UdcrOs3ZYPaHC3APBmI0KBb HrpmNgBEGMKshM/TOztlVGOSDBTanauU64m6TE7D4WmDYjHRo+zmrCOwCC7HphOamBHDFCDD 2voep2aV/sQbC+eOMxsnzweWbS8SoIs1AuiuQ/mx7Z/K+rb4CwYtZbt1Nhv4O3TkAk/9T1oA MSTy2GBVXl0nn4TSD8y3aBwvU19ykuD0KVjjPxYEttT5/xNUggkMJ7T1e16C9ToVg3dedeJT U6qQtO9Dj4pVNI+38cOY1phG9Wllh3PwjKmA6UJmLyTGJw07qXc0mDtKMlnznbG0LAtj10nQ stUKW2rnbV/9gjWB47RiUqVjaeqdaIG3C7M7miP12SOvFsLGDJ3BLjDUXEEbU/Rttn1o1nPR L62CLkhLhATmp2sMKxPP/zCo20OfOrpPNXVYn6g0zOxDhiQgKuRZo7rcGQBzQ3SD08Llw0W9 HeCcwM5A3Hy8CrlEDVyGAe3MAvX+u5kpSbnFifcrimPZkxljP+u/wINwOebU7UV164FvyEor 3N1Gky81pTYEYnIvBJvKYNbZ951+1JbzSTBrQUoP5euN+Z6m1Qacg92o1LG2BJwBYFNlMErq DUhyw8hYbmA3gZ5fiiDlYv1JqWRL2Dz+B61bKuD21rQyJCO560L6f85t0TLswauGU4v9nxm1 59e1H7Pro7SAl80VpT8Gl0y6wA8p7zeZXwl4JjI0HR3LaSumjrL2tZsBex8jxj9J5FQN6SLE AK0GMofbyS3AMotnVXhLhcNPeQJsbUxI9vjbPyenqiiIOdnmjuiy2VB+oF0lEyWpWJ6TabT0 pAJzuv9vEPPXirgjFqnrsH8mJxVLTAUEG2lzCH4BYlXLqRsdIcPAG2qLoW53NJ7z5LqXndZ8 hakCTZkkIeochSKKUTg1wlR3kULsFSoniy3yzFxmjAt6KGY2W2GwujvcgYGJn8eXHNr3jKOa cC/i9EXWlTtbhB8zkP0oxangfEF+uIidzq2Iw8AZSX9ImB8X7Hls7ODZ5UK85Y0qWBMV/z6Z 1mGS7n7qh9c0iX5HmIYyipoElPi8pj/gRF+j3qQaXhpq3+MM8B7yw+Z/MHWQf9a3yYXbCZ/j jbTC121Pt3v9tKR3cSm0Kj2Rye6W5tffDO+h4KLujP9/XBgBRy0nuyistLgFgc+3Cry1t0sX iLN5kWZAMGjx+GxNuRpeVNtDVn35p9hG41wpYA3gYkZxXkQgpj9EWMvqW7oKp0b3Kv/aCFIX jsX25vO5xCj3kR/L3WPzoa/V3OHw8InacPoKm8R3ys86YhNBsL2pPRFliVt5EKlpwbQavlhj x8Szvwh7HMfiuAN/gEqy22RD6sTEk9RISH3307Qvpbu8eMOOjjpLOD43VEb/5jpFLyYpwBAR Hv1MowvGyN99IQ3MV7B1mHy9pCxfdDRadwJsRjH2xzEjuVTNNcwjq9Q3XshaT+75CN7jbNj3 nkMldmgsYOKKntg5ve8Cx9cbXjuYt8LvyrqleBYl9qX2IamGtNgHC8KVd3mV6HNcnpauPL5O gKJCDB5pG2cHO+VHASR8AF+snjLEpuqK2C/K34ewtFvQRCcIApUhwVeD1BY1tYpUxunwsDsa hIz5zsf/hjgtxFIy+lpKwjXXWDYqwOlbz41TN6UKx8cvWQgrw/FdMeZ6Ox0BSRR+Jas+ReMJ mKsbANNFWgVW0aACgOrLvy06NLH6eTdGvumIq6Ef+CVseIHHaTtp9rnws588j2LLMnKInRyE 6hxxB9YRX4gU8XBx2dUFmpOxnqLNZLE4k/7oHE/r9jjoqq3Hli0vs3WVeMUaZI2qnXUye+CL 7LC2ng/cG4CkMtKnTiSkPAexAJA1X8oLWX8V+RY83aKFvqYm7cLXUFBLXovcpIZteRkmVAdX KyTwtLtiuwn0rhsUQoDDRq53Zj3Lc0SfzPkbAOBXRnUcuTAfXqRmon2ef/uEOILyrwF61vo/ 27cShGGXHzLliG1BUr3YKcc0WfCZkwY4MbkLV5sETSxFou4LEDrdoYm13tuhuRlznLSaTxGa GY6KRgc6ObKq3sf26QaeSQJ+HNhKaPsdz+xye7eJ95WtPJqBn8xjOdG+DEhzKMT6ihYRftzk S+Ur9h0oljgnPPdgjxgGAFDrDpGnufp9Q1rJLnZ+59cWH3F4ANF7GOeDA4PrsdkDdunsr5Zy 9zGnqb+YDlY9Nec8cwZDsnSYMWJVRhpeQLuAyLRBRAZQCSDMGjegwlcl6jX+CDN6Jc9rZfol dwFTboaHF05G/UGC1h0SdwPJJAkO1Fs2bWfjcMO+T+/tEyLHJQc7s2BD6zMR6i3e1P7xfFea hAFwK31N9EWP4z/gAl5b0Vi2Z/NAwzWVMxMpStoakk1pl9M+T5wVD5WuQqtZwWz7XsUDfPxk AQxj140YO8j7HH0/l0zJ1HLuDoYn042ltHohDmQdHj6K6L6DuQ0Q2Lk8lM8NJ/2WVM/dQqpg UltLyvJXZpUhrpkMGFs0UrS5MMJFvlbQqlJJhQXwLvEApdgmUQZoSKhy0hd4OLDApY3jwomf 6mnqHdY0h5iZto4TUQxDK9Az1wVh6XX+yH1jqY+xwgRI0tL+2SXKnZgUKMgOb4hKC6l++Vt7 UqJnD4RIQDkstIlpfVl8k44MuWEiSnn1uwbQn0= IronPort-Data: A9a23:43xDAqoIUa5R8stuHttRs1rWiBZeBmJYbhIvgKrLsJaIsI4StFCzt garIBmDMv6IZzf3Kdl3bo3i8htUvceAn9FmHVBk/iA8ECkUpOPIVI+TRqvSF3PLf5ebFCqLz O1HN4KedJhsJpP4jk3wWlQ0hSAkjclkfpKlVKiefHoZqTZMEE8JkQhkl/MynrlmiN24BxLlk d7pqqUzAnf8s9JPGjxSsvvrRC9H5qyo5GpB5gBmPJingXeH/5UrJMJHTU2OByCgKmVkNrbSb /rOyri/4lTY838FYj9yuuuTnuUiG9Y+DCDW4pZkc/DKbitq+kTe5p0G2M80Mi+7vdkmc+dZk 72hvbToIesg0zaldO41C3G0GAkmVUFKFSOuzdFSfqV/wmWfG0YAzcmCA2kfbNIKxbhsOlpc2 qQ9dQ8IdUDem82flefTpulE3qzPLeHuNYIb/3BnlHTXUK5gTpfETKHHo9Rf2V/chOgURaeYN 5dfMGQxKkmYC/FMEg9/5JYWneymnj/nbjdcqVmUubsf7G/Uwwh81bHsNJzefdniqcB9xx7A+ TqXojqjav0cHIHY0yGo9Sj3uuvGwhjJeYgoNKSop9c/1TV/wURIVUROCgrlyRWjsWa1Utdbb kgV4TYGtrk37EXtT9/nXhT+rmTsg/IHc99ZEul/6QbUj6SJu0CWAW8LSjMHY9sj3CMredA0/ nbYwMHWWydUi6+6EVfAybKP/W6uFgFAeAfuehQ4ZQcC5tDipqQ6gRTOUstvHcaJYjvdSWGYL 9ei/HhWulkDsfPnwZlX6rwuvt5Bjp3ATwpw5wKOG2z4tkV2Y4mqY4Hu4l/ehRqhEGp7Zgjd1 JTns5HBhAzrMX1rvHHQKAnqNOz2j8tpyBWG3TZS82AJrlxBAUKLc4FK+y1ZL0x0KMsCcjKBS BaM4lsPuc8MYiDxM/Qfj2eN5yICnfiI+TPNBqG8UzaySsEgHON61HgxNR7OgDq1+KTSufhuZ c7FIK5A8kr2+Yw8kWPuGLZDuVPa7i85wmzXSNj6yR/huYdyl1bEIYrpxGCmN7hjhIvd+Fu92 48Ga6OilU8DOMWgOXK/2dBIcjg3wY0TX8GeRzp/LbbbelIO9aBII6O5/I7NjKQ8z/kIxreYp SHVt40x4AOXuEAr4D6iMhhLAI4Dl74lxZ7iFXV0YQj66Gtpeou18qYUer0+eLRtpqQpzud5Q 7NBM4+MC+hGAGaPsTkMT4jPnKo7fjSShCWKI3WEZho7dMVeXADnwILvUTbu0ygsNRCJk/UCj Yeu7S7heqpbdT9eVJ7XTNmN02KOuWMsnbMufknQffhWVkbe0KlrDC3TiPVtcscGBivf9wSez CKTJwkSnsjWgooP6NKSr7u1n4SoNOpfH0RhAGjQ64itBxTa5maOxYxhUv6CWDLgCEfYxf2HX vpE6N3ZK9sFl0Zun6smNo103IQs49fLjJ1L/DRORXnkQQyiNeJ9HyOgw8JKiJxo+pZYngmTA Wek5dhQPOSyCvPPSVI+ClIsUbWe6KsyhDLX0PUSJXf67g9R+J6scx1bHzuIuRxnAIpFCqEX6 sZ/h5dO8C26sAQgDfiehCMN92isEG0JY596ir4kWr3UmigZ4XAcR6fDCx3GwoCFMPRNFUgIH gW6poT/g5Zk+06TVEZrSFbs27JGiIUsqSJ66gYIB260l+rvgt412xxs8goLcDlF8yUf08xPF zhqE2ZXOZSx+yxZgZkffmK0RCBEKh6r2m3w7ForiFzmS1KMaWjTCVZkPMCx1V0rqTNCTGJL+ JWd7njvahfxXcTLxiBpc1VUm//iat1Q9wP5h8GsGfqeLaQ6eTbIhqyPZ3ICjgnOW+cdtRbin vZ72tpwZYnQFz8ik4diB6a0jb0vGQ25fkpcSvRfzYY1NGD7egDq/wORKkq0K/h/F9aT/WCWU 8VRd99yDTKg3yOzrxceN64GA5lwuNULvNMiWLfaFVQqgouljAhCkczvr3DlpWoRXd9Rv943K drRexK8A2WgvyZotFGXnvZUGFiTQIciXxL97tCX4e9SNpMkscNQS28Q/IawnU2oNFpAw0rJk iLFP7Tb3s5z+7RKxoHMKJhONy+wCNH0VdmLzjyNjsRzXYvxFvnK5iwoqQjBHgVJPLEudcx9u paTvfXWgk7UnrYEfFrIupuGFpsTtNuABvpTOP3ZNHNxwCmIApftxzAh+GmID4NDv/0Ax8ugR iq+MNCRc/xMUfhj5XRlUQpsODdDNLbWN4DLunqbg9mXLxoSwyjrHYiCzmD4S2N2bQoKMMDOM RD1sPOQ+dxoloRAKxsaDfVAAZUjAlvcdYY5Vt/2px+KJ3KJhw6ch77cihYQ0zHHJX2aGsLc4 5ieZBzfdgy3iZ7Y3uNirI1+kR0GPklT2dBqUBomxOd3rDSmAEotD+cXa8wGA64JtB3C7sjzY TWVYVYyDSn4Yy9/Tiz9x9beRSaaOP0FP4boBz4u/n7MURyMOqG7POJD+BtjslBMQRmy/NH/f Jtasjf1MwOqy55kefcL67bpya17z/fd3TQT9Vq7j8X2BA0EDK4X0GB6WjBATjHDD9qHgXCjy bLZnoyYaBrTpY/N/cdcl7p9HRgYuHbuyGxtY3rXhtnYvIqfwatLz/iX1yQfFFEcRJxiGVLMb Sqfq6ixD6S+1XsUtq8kvtsohel/Dvfj8g2SMvr4XQNL902vwj1PAi7B9BbjiOkt/wlQF17Yn ziopXM5ASxp7ayXNKK+kW00xn66bp7A4/wlQuIySf8qXCHVF+TkRiU= IronPort-HdrOrdr: A9a23:b/eU06PZ4fKJucBcTuCjsMiBIKoaSvp033AB3UoZc20tTiX4rb HJoB1/73XJYVkqKRMdcLy7Scq9qBDnlaKdg7NhWItKNTOO0ACVxepZnO/fKlPbakrD398Y+q F6baBkBdH8SXR8h93r+RS1Hr8brOVvM5rGuQ4d9RpQpM1RBZ2IJj0ZNjqm X-Talos-CUID: 9a23:X4apUm10s/vL97w+WZ7347xfM5F6YEKD10zrMWDgLDtWTabFFEO/0fYx X-Talos-MUID: 9a23:wIm9PgmACctcyKm7MEHBdno/c91zzqP0U3wJmMo9ieiODwxpK2a02WE= X-IronPort-Anti-Spam-Filtered: true X-IronPort-AV: E=Sophos;i="6.11,257,1725314400"; d="scan'208,217";a="100709562" X-MGA-submission: =?us-ascii?q?MDFX8RlhdA1YBxxkQ7x5cb5yEHQwdumEGFahc7?= =?us-ascii?q?5weT2oSTiL6dmjdj1I1AURsR1Igc4jq8pncbSwiZ3w3bP7KnFMeTkvpw?= =?us-ascii?q?6ht8UxB9xNhIXuaPLci5dqfi8k+VJfS/sMcBCPpFQ/NbZgpvQvYOJGCq?= =?us-ascii?q?mKi0qOFwK8Oib3Bj85SlVUDQ=3D=3D?= Received: from mail-io1-f50.google.com ([209.85.166.50]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Nov 2024 17:35:47 +0100 Received: by mail-io1-f50.google.com with SMTP id ca18e2360f4ac-83b430a4cfdso216462639f.2 for ; Mon, 04 Nov 2024 08:35:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1730738146; x=1731342946; darn=inria.fr; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ZfczDQYVMMTKcmxtmRdJREEnsWo+JIkDkgMmU4FYaXQ=; b=JIkTn2K2dKx8uE7ddmK8YNb7SJSawFdAfRydC7gYSblRi3nw8voue+G+zIhUEc43b6 +0RgBJ/phFIvKLJ84dJOzc71n6YCW453rt3vVyXK0jHD0HFdtRg7doSSCnGTbTSgFp/O /m0fjsImC4NvLJ6gmqBA7TjiZuhedx+Ge2BvWqbgxQxWTtsJXJegQywQMd5XZxL9RcX0 cX+MSNE95/l4O6ij/yFrYWjHn5FPCryFNn7bI5sQA/oorefgaekrn+XYs7nK285NSs/C 2bGoGRKGj+YPFyXcm6Ivld8Vneea7LvgMPB72kYtEeLjQ4xX6YIX8ysruXdJ5P03wh1J oofA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730738146; x=1731342946; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZfczDQYVMMTKcmxtmRdJREEnsWo+JIkDkgMmU4FYaXQ=; b=fwjo1ahN/2VwGFYjwwslpgrsb87ETCj3goC4a50CK3GJHJ23UykK7GG6z8TknVk1uu DwvQ/SDL02eu6vW+jEzNS/QJOdGHUQcAOhViU7iZmer8u0tX3lO7EXlKZL7peOdkM3Pc npT4gIZ51waNIyhNZJ6CPggANTtfBiyXpkXlzfGcBRcxN9ULjeFoRuHm+uQ4ly0hrc+A 3bIV7QfhBBEMsKieMvoe4SMDQ+LFf9IlVy+ZUBJFBGkP5iADYtuVlk0AgVu4piSM/mts DYrjE6k3tSQA0ConZz/BAJcxV6a7f/rl0acdFmLrGWfN7fWEYL8EL05tAtvBvEgf7P8L NRDw== X-Forwarded-Encrypted: i=1; AJvYcCVAFH0sJYK+eoFE8JdQtopDh5zyVCs5eGN4iuGfuxZvw9SFYgCYi9FYSIm99yzmmGSPsh9W8zoL3oQ=@inria.fr X-Gm-Message-State: AOJu0YzeljHihR4OKXjy4lOyBbfXeiUUwsV5veZxOvLWompphFHIbfBq yi0OtsL7mh30WkZcfasawHl10VpTLBRMe7Hnn83olDsYObLnUiQhuKD55da1f+Z9GOjS81WAdaZ Qq2SK/ow7sgtLdeDfNJxchXXKh9U= X-Google-Smtp-Source: AGHT+IGwYwVuiVfR2mIYaZ/0z9g4SL1pIIIFULuUi1zkPsbmI1M1NZnRWxEk64CBAtXq47L5HBcDliui+IdVXM7BD9k= X-Received: by 2002:a05:6602:6d16:b0:82a:7181:200f with SMTP id ca18e2360f4ac-83b1c45938amr3268198039f.9.1730738145405; Mon, 04 Nov 2024 08:35:45 -0800 (PST) MIME-Version: 1.0 From: ICFP Publicity Date: Mon, 4 Nov 2024 11:35:33 -0500 Message-ID: To: undisclosed-recipients:; Content-Type: multipart/alternative; boundary="0000000000005b34c0062618e04f" Subject: [Caml-list] ICFP 2025: Call for Papers Reply-To: ICFP Publicity X-Loop: caml-list@inria.fr X-Sequence: 19194 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: --0000000000005b34c0062618e04f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable PACMPL Volume 7, Issue ICFP 2025 Call for Papers Accepted papers to be invited for presentation at The 30th ACM SIGPLAN International Conference on Functional Programming October 12-18, 2025 Singapore https://icfp25.sigplan.org/ ### Important Dates and Deadlines Paper Submissions: February 27, 2025 Author Response: April 28 - May 1, 2025 Notifications of Acceptance: May 23, 2025 All deadlines are Anywhere on Earth (AoE). Conference dates: October 12-18, 2025 ### New This Year For the first time, ICFP will be co-located with SPLASH! https://conf.researchr.org/home/icfp-splash-2025 Note that the conference will be held in October this year, instead of September. The conference dates are October 12-18, 2025. ### Scope PACMPL issue ICFP 2025 seeks original papers on the art and science of functional programming. Submissions are invited on all topics from principles to practice, from foundations to features, and from abstraction to application. The scope includes all languages that encourage functional programming, including both purely applicative and imperative languages, as well as languages with objects, concurrency, or parallelism. Topics of interest include (but are not limited to): * Language Design: concurrency, parallelism, and distribution; modularity; components and composition; meta-programming; macros; pattern matching; typ= e systems; type inference; dependent types; effect types; gradual types; refinement types; session types; interoperability; domain-specific languages; imperative programming; object-oriented programming; logic programming; probabilistic programming; reactive programming; generic programming; bidirectional programming. * Implementation: abstract machines; virtual machines; interpretation; compilation; compile-time and run-time optimisation; garbage collection and memory management; runtime systems; multi-threading; exploiting parallel hardware; interfaces to foreign functions, services, components, or low-level machine resources. * Software-Development Techniques: algorithms and data structures; design patterns; specification; verification; validation; proof assistants; debugging; testing; tracing; profiling; build systems; program synthesis. * Foundations: formal semantics; lambda calculus; program equivalence; rewriting; type theory; logic; category theory; computational effects; continuations; control; state; names and binding; program verification. * Analysis and Transformation: control flow; data flow; abstract interpretation; partial evaluation; program calculation. * Applications: symbolic computing; formal-methods tools; artificial intelligence; systems programming; distributed systems and web programming; hardware design; databases; scientific and numerical computing; graphical user interfaces; graphics and multimedia; GPU programming; scripting; system administration; security. * Education: teaching introductory programming; mathematical proof; algebra= . Submissions will be evaluated according to their relevance, correctness, significance, originality, and clarity. Each submission should explain its contributions in both general and technical terms, clearly identifying what has been accomplished, explaining why it is significant, and comparing it with previous work. The technical content should be accessible to a broad audience. PACMPL issue ICFP 2025 also welcomes submissions in two separate categories =E2=80=94 Functional Pearls and Experience Reports =E2=80=94 that must be marked as s= uch when submitted and that need not report original research results. Detailed guidelines on both categories are given at the end of this call. In an effort to achieve a balanced, diverse program, each author may be listed as a (co)author on a maximum of four submissions. Authors who require financial support to attend the conference can apply for PAC funding (http://www.sigplan.org/PAC/). The General Chair and PC Chair may not submit papers. PC members (other than the PC Chair) may submit papers. Please contact the Program Chair if you have questions or are concerned about the appropriateness of a topic. ### Full Double-Blind Reviewing Process ICFP 2025 will use a full double-blind reviewing process (similar to the on= e used for ICFP 2024 but different from the lightweight double-blind process used in previous years). This means that identities of authors will not be made visible to reviewers until after conditional-acceptance decisions have been made, and then only for the conditionally-accepted papers. The use of full double-blind reviewing has several consequences for authors. *Submissions*: Authors must omit their names and institutions from their paper submissions. In addition, references to authors=E2=80=99 own prior work sho= uld be in the third person (e.g., not "We build on our previous work ..." but rather "We build on the work of ..."). *Supplementary material*: Authors must fully anonymize any supplementary material (see below). Links to supplementary material on external websites are not permitted. *Author response*: In responding to reviews, authors should not say anythin= g that reveals their identity, since author identities will not be revealed t= o reviewers at that stage of the reviewing process. *Dissemination of work under submission*: Authors are welcome to disseminat= e their ideas and post draft versions of their paper(s) on their personal website, institutional repository, or arXiv (reviewers will be asked to turn off arXiv notifications during the review period). But authors should not take steps that would almost certainly reveal their identities to members of the Program Committee, e.g., directly contacting PC members or publicizing the work on widely-visible social media or major mailing lists used by the community. The purpose of the above restrictions is to help the Program Committee and external reviewers come to a judgment about the paper without bias, not to make it impossible for them to discover the authors=E2=80=99 identities if they = were to try. In particular, nothing should be done in the name of anonymity that weakens the quality of the submission. However, there are occasionally cases where adhering to the above restrictions is truly difficult or impossible for one reason o= r another. In such cases, the authors should contact the Program Chair to discuss the situation and how to handle it. The FAQ on Double-Blind Reviewing ( https://popl24.sigplan.org/track/POPL-2024-popl-research-papers#FAQ-on-Doub= le-Blind-Reviewing ) addresses many common scenarios and answers many common questions about thi= s topic. But there remain many grey areas and trade-offs. If you have any doubts about how to interpret the double-blind rules or you encounter a complex case that is not clearly covered by the FAQ, please contact the Program Chair fo= r guidance. ### Preparation of submissions *Deadline*: The deadline for submissions is Thursday, 27 February, 2025, Anywhere on Earth (https://www.timeanddate.com/time/zones/aoe). This deadline will be strictly enforced. *Formatting*: Submissions must be in PDF format, printable in black and white on US Letter sized paper and interpretable by common PDF tools. All submission= s must adhere to the "ACM Small" template that is available (in both LaTeX an= d Word formats) from https://www.acm.org/publications/authors/submissions. Please download the latest version of the ACM style from https://www.acm.org/publications/authors/submissions, since the citation format has recently been changed. See also PACMPL=E2=80=99s Information and Guidelines for Authors at https://pacmpl.acm.org/authors.cfm. There is a limit of 25 pages for a full paper or Functional Pearl and 12 pages for an Experience Report; in either case, the bibliography and an optional clearly marked appendix will not be counted against these limits. Submissions that exceed the page limits or, for other reasons, do not meet the requirements for formatting, will be summarily rejected. *Submission*: Submissions will be accepted at https://icfp25.hotcrp.com/ Improved versions of a paper may be submitted at any point before the submission deadline using the same web interface. *Author Response Period*: Authors will have a 96-hour period, starting at 00:00 (midnight) AOE on Monday, 28 April, 2025, to read reviews and respond to them. *Appendix and Supplementary Material*: Authors have the option to include a clearly marked appendix and/or to attach supplementary material to a submission, on the understanding that reviewers may choose not to look at such an appendix or supplementary material. Supplementary material may be uploaded as a separate PDF document or tarball. Any supplementary material must be uploaded at submission time, not by providing a URL in the paper that points to an external repository. All supplementary material must be anonymised. *Authorship Policies*: All submissions are expected to comply with the ACM Policies for Authorship that are detailed at https://www.acm.org/publications/authors/information-for-authors. *Republication Policies*: Each submission must adhere to SIGPLAN=E2=80=99s republication policy, as explained on the web at http://www.sigplan.org/Resources/Policies/Republication. ### Review Process This section outlines the two-stage process with double-blind reviewing tha= t will be used to select papers for PACMPL issue ICFP 2025. Like last year, ICFP 2025 will adapt a full double-blind reviewing process. More information see below. ICFP 2025 will have an Associate Chair who will help the PC Chair monitor reviews, solicit external expert reviews for submissions when there is not enough expertise on the committee, and facilitate reviewer discussions. ICFP 2025 will employ a two-stage review process. The first stage in the review process will assess submitted papers using the criteria stated above and will allow for feedback and input on initial reviews through the author response period mentioned previously. As a result of the review process, a set of papers will be conditionally accepted and all other papers will be rejected. Authors will be notified of these decisions on 23 May, 2025. Authors of conditionally accepted papers will be provided with committee reviews along with a set of mandatory revisions. By 12 June, 2025, the authors should provide a second revised submission. The second and final reviewing phase assesses whether the mandatory revisions have been adequately addressed by the authors and thereby determines the final accept/reject status of the paper. The intent and expectation is that the mandatory revisions can feasibly be addressed within three weeks. The second submission should clearly identify how the mandatory revisions were addressed. To that end, the second submission must be accompanied by a cove= r letter mapping each mandatory revision request to specific parts of the paper. The cover letter will facilitate a quick second review, allowing for confirmation of final acceptance within two weeks. Conversely, the absence of a cover letter will be grounds for the paper=E2=80=99s rejection. ### Information for Authors of Accepted Papers * As a condition of acceptance, final versions of all papers must adhere to the ACM Small format. The page limit for the final versions of papers will be increased by two pages to help authors respond to reviewer comments and mandatory revisions: 27 pages plus bibliography for a regular paper or Functional Pearl, 14 pages plus bibliography for an Experience Report. * Authors of accepted submissions will be required to agree to one of the three ACM licensing options, one of which is Creative Commons CC-BY publication; this is the option recommended by the PACMPL editorial board. A reasoned argument in favour of this option can be found in the article Why CC-BY? published by OASPA, the Open Access Scholarly Publishers Association. The other options are copyright transfer to ACM or retaining copyright but granting ACM exclusive publication rights. * PACMPL is a Gold Open Access journal, and authors are encouraged to publish their work under a CC-BY license. Gold Open Access guarantees permanent fre= e online access to the definitive version in the ACM Digital Library, and the recommended CC-BY option also allows anyone to copy and distribute the work with attribution. Gold Open Access has been made possible by generous funding through ACM SIGPLAN, which will cover all open access costs in the event authors cannot. Authors who can cover the costs may do so by paying an Article Processing Charge (APC). PACMPL, SIGPLAN, and ACM Headquarters are committe= d to exploring routes to making Gold Open Access publication both affordable and sustainable. * ACM Author-Izer is a unique service that enables ACM authors to generate and post links on either their home page or institutional repository for visitors to download the definitive version of their articles from the ACM Digital Library at no charge. Downloads through Author-Izer links are captured in official ACM statistics, improving the accuracy of usage and impact measurements. Consistently linking to the definitive version of an ACM article should reduce user confusion over article versioning. After an article has been published and assigned to the appropriate ACM Author Profile pages, authors should visit http://www.acm.org/publications/acm-author-izer-servic= e to learn how to create links for free downloads from the ACM DL. * The official publication date is the date the papers are made available in the ACM Digital Library. This date may be up to two weeks prior to the first da= y of the conference. The official publication date affects the deadline for any patent filings related to published work. * Authors of each accepted submission are invited to attend and be available for the presentation of that paper at the conference. The schedule for presentations will be determined and shared with authors after the full program has been selected. *ORCID*: ORCID provides a persistent digital identifier (an ORCID iD) that you own and control, and that distinguishes you from every other researcher: https://orcid.org/. ACM now require an ORCID iD for every author of a paper, not just the corresponding author. So, the author who is filling out the permission form should make sure they have the ORCID iDs for all of their coauthors before filling out the form. Any authors who do not yet have an ORCID iD can go to https://orcid.org/register to have one assigned. ### Artifact Evaluation Authors of papers that are conditionally accepted in the first phase of the review process will be encouraged (but not required) to submit supporting materials for Artifact Evaluation. These items will then be reviewed by an Artifact Evaluation Committee, separate from the paper Review Committee, whose task is to assess how the artifacts support the work described in the associated paper. Papers that go through the Artifact Evaluation process successfully will receive a seal of approval printed on the papers themselves. Authors of accepted papers will be encouraged to make the supporting materials publicly available upon publication of the papers, for example, by including them as "source materials" in the ACM Digital Library. An additional seal will mark papers whose artifacts are made available, as outlined in the ACM guidelines for artifac= t badging. Participation in Artifact Evaluation is voluntary and will not influence th= e final decision regarding paper acceptance. ### Special categories of papers In addition to research papers, PACMPL issue ICFP solicits two kinds of papers that do not require original research contributions: Functional Pearls, which are full papers, and Experience Reports, which are limited to half the length of a full paper. Authors submitting such papers should consider the following guidelines. ### Functional Pearls A Functional Pearl is an elegant essay about something related to functiona= l programming. Examples include, but are not limited to: * a new and thought-provoking way of looking at an old idea * an instructive example of program calculation or proof * a nifty presentation of an old or new data structure * an interesting application of functional programming techniques * a novel use or exposition of functional programming in the classroom While pearls often demonstrate an idea through the development of a short program, there is no requirement or expectation that they do so. Thus, they encompass the notions of theoretical and educational pearls. Functional Pearls are valued as highly and judged as rigorously as ordinary papers, but using somewhat different criteria. In particular, a pearl is no= t required to report original research, but, it should be concise, instructive, and entertaining. A pearl is likely to be rejected if its readers get bored, if the material gets too complicated, if too much-specialised knowledge is needed, or if the writing is inelegant. The key to writing a good pearl is polishing. A submission that is intended to be treated as a pearl must be marked as such on the submission web page and should contain the words "Functional Pearl" somewhere in its title or subtitle. These steps will alert reviewers to use the appropriate evaluation criteria. Pearls will be combined with ordinary papers, however, for the purpose of computing the conference=E2=80=99s acceptance r= ate. ### Experience Reports The purpose of an Experience Report is to describe the experience of using functional programming in practice, whether in industrial application, tool development, programming education, or any other area. Possible topics for an Experience Report include, but are not limited to: * insights gained from real-world projects using functional programming * comparison of functional programming with conventional programming in the context of an industrial project or a university curriculum * project-management, business, or legal issues encountered when using functional programming in a real-world project * curricular issues encountered when using functional programming in education * real-world constraints that created special challenges for an implementation of a functional language or for functional programming in general An Experience Report is distinguished from a normal PACMPL issue ICFP paper by its title, by its length, and by the criteria used to evaluate it. * Both in the papers and in any citations, the title of each accepted Experience Report must end with the words "(Experience Report)" in parentheses. The acceptance rate for Experience Reports will be computed and reported separately from the rate for ordinary papers. * Experience Report submissions can be at most 12 pages long, excluding bibliography. * Each accepted Experience Report will be presented at the conference, but depending on the number of Experience Reports and regular papers accepted, authors of Experience Reports may be asked to give shorter talks. * Because the purpose of Experience Reports is to enable our community to understand the application of functional programming, an acceptable Experience Report need not add to the body of knowledge of the functional-programming community by presenting novel results or conclusions. It is sufficient if the report describes an illuminating experience with functional programming, or provides evidence for a clear thesis about the use of functional programming. The experience or thesis must be relevant to ICFP, but it need not be novel= . The review committee will accept or reject Experience Reports based on whether they judge the paper to illuminate some aspect of the use of functional programming. Anecdotal evidence will be acceptable provided it is well-argued and the author explains what efforts were made to gather as much evidence a= s possible. Typically, papers that show how functional programming was used are more convincing than papers that say only that functional programming was used. It can be especially effective to present comparisons of the situations before and after the experience described in the paper, but other kinds of evidenc= e would also make sense, depending on context. Experience drawn from a single person=E2=80=99s experience may be sufficient, but more weight will be give= n to evidence drawn from the experience of groups of people. An Experience Report should be short and to the point. For an industrial project, it should make a claim about how well functional programming worked and why; for a pedagogy paper, it might make a claim about the suitability of a particular teaching style or educational exercise. Either way, it should produce evidence to substantiate the claim. If functional programming worked in thi= s case in the same ways it has worked for others, the paper need only summarise the results =E2=80=94 the main part of the paper should discuss how well it= worked and in what context. Most readers will not want to know all the details of the experience and its implementation, but the paper should characterise it and its context well enough so that readers can judge to what degree this experience is relevant to their own circumstances. The paper should take care to highlight any unusual aspects; specifics about the experience are more valuable than generalities about functional programming. If the paper not only describes experience but also presents new technical results, or if the experience refutes cherished beliefs of the functional-programming community, it may be better to submit it as a full paper, which will be judged by the usual criteria of novelty, originality, and relevance. The Program Chair will be happy to advise on any concerns about which category to submit to. ### About PACMPL Proceedings of the ACM on Programming Languages (PACMPL https://pacmpl.acm.org/) is a Gold Open Access journal publishing research on all aspects of programming languages, from design to implementation and from mathematical formalisms t= o empirical studies. Each issue of the journal is devoted to a particular subject area within programming languages and will be announced through publicised Calls for Papers, like this one. ### ICFP Organizers General Chair: Ilya Sergey (NUS) Program Chair: Dominique Devriese (KU Leuven) Associate Program Chair: Peter Thiemann (University of Freiburg) Workshops Co-Chairs: Ben Greenman (University of Utah) Chandrakana Nandi (Certora) Artifact Evaluation Co-Chairs: Beno=C3=AEt Montagu (INRIA) Lionel Parreaux (HKUST) Industrial Relations Chair: Daniel Winograd-Cort (Nectry Inc.) Student Volunteer Chair: Joe Watt (Institute for Infocomm Research, A*STAR) SRC Co-Chair: Kuen-Bang Hou (Favonia) (University of Minnesota) Publicity Chair: Sam Westrick (NYU) Diversity Co-Chairs: Alejandro Russo (Chalmers, DPella) KC Sivaramakrishnan (Tarides, IIT Madras) Web Chair: Jules Jacobs (Cornell) Doctoral Symposium Chair: Conrad Watt (Nanyang Technological University) Programming Contest Organizer: Liam O'Connor (Australian National University) SIGPLAN Conference Manager: Neringa Young --0000000000005b34c0062618e04f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
PACMPL Volume 7, Issue ICFP 2025

=
Call for Papers

Accept= ed papers to be invited for presentation at
The 30th = ACM SIGPLAN International Conference on Functional Programming
= October 12-18, 2025
= Singapore


### Important Dates and Deadlines=

Paper Submissions: February 27, 2025
Author= Response: April 28 - May 1, 2025
Notifications of Acceptance: Ma= y 23, 2025

All deadlines are Anywhere on Earth (AoE).
Conference dates: October 12-18, 2025

### New This Year

= For the first time, ICFP will be co-located with SPLASH!

Note that the conference wil= l be held in October this year, instead of
September. The confere= nce dates are October 12-18, 2025.

### Scope

PACMPL issue ICFP= 2025 seeks original papers on the art and science of
functional = programming. Submissions are invited on all topics from principles to
=
practice, from foundations to features, and from abstraction to applic= ation. The
scope includes all languages that encourage functional= programming, including
both purely applicative and imperative la= nguages, as well as languages with
objects, concurrency, or paral= lelism. Topics of interest include (but are not
limited to):
* Language Design: con= currency, parallelism, and distribution; modularity;
components= and composition; meta-programming; macros; pattern matching; type
systems; type inference; dependent types; effect types; gradual types;<= /div>
refinement types; session types; interoperability; domain-speci= fic languages;
imperative programming; object-oriented programm= ing; logic programming;
probabilistic programming; reactive pro= gramming; generic programming;
bidirectional programming.
=
* Implementation: abstr= act machines; virtual machines; interpretation;
compilation; co= mpile-time and run-time optimisation; garbage collection and
me= mory management; runtime systems; multi-threading; exploiting parallel
hardware; interfaces to foreign functions, services, components, or= low-level
machine resources.

* Software-Development Techniques: algorithms and d= ata structures; design
patterns; specification; verification; v= alidation; proof assistants;
debugging; testing; tracing; profi= ling; build systems; program synthesis.

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

* Analysis and Transformation: control flow; data flow; ab= stract interpretation;
partial evaluation; program calculation.=

* Applications: s= ymbolic computing; formal-methods tools; artificial
intelligenc= e; systems programming; distributed systems and web programming;
= hardware design; databases; scientific and numerical computing; graphical= user
interfaces; graphics and multimedia; GPU programming; scr= ipting; system
administration; security.

* Education: teaching introductory progr= amming; mathematical proof; algebra.

Submissions will be eval= uated according to their relevance, correctness,
significance, or= iginality, and clarity. Each submission should explain its
contri= butions in both general and technical terms, clearly identifying what has
been accomplished, explaining why it is significant, and comparing= it with
previous work. The technical content should be accessibl= e to a broad audience.

PACMPL issue ICFP 2025 also welcomes s= ubmissions in two separate categories =E2=80=94
Functional Pearls= and Experience Reports =E2=80=94 that must be marked as such when
submitted and that need not report original research results. Detailed
guidelines on both categories are given at the end of this call.
In an effort to achieve a balanced, diverse program, each autho= r may be listed
as a (co)author on a maximum of four submissions.= Authors who require financial
support to attend the conference c= an apply for PAC funding

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

Please contact the Program Chair if you ha= ve questions or are concerned about
the appropriateness of a topi= c.

### Fu= ll Double-Blind Reviewing Process

ICFP 2025 will use a= full double-blind reviewing process (similar to the one
used for= ICFP 2024 but different from the lightweight double-blind process used
in previous years). This means that identities of authors will not b= e made
visible to reviewers until after conditional-acceptance de= cisions have been
made, and then only for the conditionally-accep= ted papers. The use of full
double-blind reviewing has several co= nsequences for authors.

*Su= bmissions*: Authors must omit their names and institutions from thei= r paper
submissions. In addition, references to authors=E2=80=99 = own prior work should be in the
third person (e.g., not "We = build on our previous work ..." but rather "We build
on= the work of ...").

*S= upplementary material*: Authors must fully anonymize any supplementa= ry
material (see below). Links to supplementary material on exter= nal websites are
not permitted.

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

*Disse= mination of work under submission*: Authors are welcome to dissemina= te
their ideas and post draft versions of their paper(s) on their= personal website,
institutional repository, or arXiv (reviewers = will be asked to turn off arXiv
notifications during the review p= eriod). But authors should not take steps that
would almost certa= inly reveal their identities to members of the Program
Committee,= e.g., directly contacting PC members or publicizing the work on
= widely-visible social media or major mailing lists used by the community.
The purpose of the above restrictions is to help the Program C= ommittee and
external reviewers come to a judgment about the pape= r without bias, not to make
it impossible for them to discover th= e authors=E2=80=99 identities if they were to try.
In particular,= nothing should be done in the name of anonymity that weakens the
quality of the submission. However, there are occasionally cases where adh= ering
to the above restrictions is truly difficult or impossible = for one reason or
another. In such cases, the authors should cont= act the Program Chair to discuss
the situation and how to handle = it. The FAQ on Double-Blind Reviewing
addresses many common scenarios and = answers many common questions about this
topic. But there remain = many grey areas and trade-offs. If you have any doubts
about how = to interpret the double-blind rules or you encounter a complex case
that is not clearly covered by the FAQ, please contact the Program Chair= for
guidance.

### Preparation of submissions

*Deadline*: The deadline for submissions = is Thursday, 27 February, 2025,
Anywhere on Earth (https://www.timeanddate.com/time/z= ones/aoe). This deadline
will be strictly enforced.

=
*Formatting*: Submissions mus= t be in PDF format, printable in black and white on
US Letter siz= ed paper and interpretable by common PDF tools. All submissions
m= ust adhere to the "ACM Small" template that is available (in both= LaTeX and

Please download the latest version of the ACM st= yle from
has recently been changed.

See al= so PACMPL=E2=80=99s Information and Guidelines for Authors at

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

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

<= div>Improved versions of a paper may be submitted at any point before the s= ubmission
deadline using the same web interface.

*Author Response Period*: Authors wi= ll have a 96-hour period, starting at 00:00
(midnight) AOE on Mon= day, 28 April, 2025, to read reviews and respond to them.

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

*A= uthorship Policies*: All submissions are expected to comply with the= ACM
Policies for Authorship that are detailed at
*Republication Policies*: Ea= ch submission must adhere to SIGPLAN=E2=80=99s republication
poli= cy, as explained on the web at

### Review Process

This section outlines th= e two-stage process with double-blind reviewing that
will be used= to select papers for PACMPL issue ICFP 2025. Like last year, ICFP
2025 will adapt a full double-blind reviewing process. More information s= ee
below.

ICFP 2025 will have an Associate Chair wh= o will help the PC Chair monitor
reviews, solicit external expert= reviews for submissions when there is not
enough expertise on th= e committee, and facilitate reviewer discussions.

ICFP 2025 w= ill employ a two-stage review process. The first stage in the review
<= div>process will assess submitted papers using the criteria stated above an= d will
allow for feedback and input on initial reviews through th= e author response
period mentioned previously. As a result of the= review process, a set of papers
will be conditionally accepted a= nd all other papers will be rejected. Authors
will be notified of= these decisions on 23 May, 2025.

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

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

### Information for A= uthors of Accepted Papers

* As a condition of acceptance, final versions of all papers= must adhere to the
ACM Small format. The page limit for the fi= nal versions of papers will be
increased by two pages to help a= uthors respond to reviewer comments and
mandatory revisions: 27= pages plus bibliography for a regular paper or
Functional Pear= l, 14 pages plus bibliography for an Experience Report.

* Authors of accepted submissions wil= l be required to agree to one of the three
ACM licensing option= s, one of which is Creative Commons CC-BY publication;
this is = the option recommended by the PACMPL editorial board. A reasoned
= argument in favour of this option can be found in the article Why CC-BY?<= /div>
published by OASPA, the Open Access Scholarly Publishers Associ= ation. The
other options are copyright transfer to ACM or retai= ning copyright but
granting ACM exclusive publication rights.
* PACMPL is a Gold = Open Access journal, and authors are encouraged to publish
thei= r work under a CC-BY license. Gold Open Access guarantees permanent free
online access to the definitive version in the ACM Digital Librar= y, and the
recommended CC-BY option also allows anyone to copy = and distribute the work
with attribution. Gold Open Access has = been made possible by generous funding
through ACM SIGPLAN, whi= ch will cover all open access costs in the event
authors cannot= . Authors who can cover the costs may do so by paying an Article
= Processing Charge (APC). PACMPL, SIGPLAN, and ACM Headquarters are commit= ted
to exploring routes to making Gold Open Access publication = both affordable and
sustainable.

* ACM Author-Izer is a unique service that enabl= es ACM authors to generate and
post links on either their home = page or institutional repository for visitors
to download the d= efinitive version of their articles from the ACM Digital
Librar= y at no charge. Downloads through Author-Izer links are captured in
official ACM statistics, improving the accuracy of usage and impact
measurements. Consistently linking to the definitive version of a= n ACM article
should reduce user confusion over article version= ing. After an article has
been published and assigned to the ap= propriate ACM Author Profile pages,
to learn how to = create links for free downloads from the ACM DL.

* The official publication date is the date= the papers are made available in the
ACM Digital Library. This= date may be up to two weeks prior to the first day
of the conf= erence. The official publication date affects the deadline for any
patent filings related to published work.

* Authors of each accepted submission are invit= ed to attend and be available for
the presentation of that pape= r at the conference. The schedule for
presentations will be det= ermined and shared with authors after the full
program has been= selected.

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

### Artifact Evaluation
<= br>
Authors of papers that are conditionally accepted in the first phas= e 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, separa= te from the paper Review Committee, whose
task is to assess how t= he artifacts support the work described in the associated
paper. = Papers that go through the Artifact Evaluation process successfully will
receive a seal of approval printed on the papers themselves. Author= s of accepted
papers will be encouraged to make the supporting ma= terials publicly available
upon publication of the papers, for ex= ample, by including them as "source
materials" in the A= CM Digital Library. An additional seal will mark papers whose
art= ifacts are made available, as outlined in the ACM guidelines for artifact
badging.

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

### Special categories of papers

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

### Functional Pearls
A Functional Pearl is an elegant essay about something related to fun= ctional
programming. Examples include, but are not limited to:
* a new and thought-= provoking way of looking at an old idea
* an instructive example of program calculation or proof<= /div>
* a nifty presentation= of an old or new data structure
* an interesting application of functional programming technique= s
* a novel use or exp= osition of functional programming in the classroom

While pear= ls often demonstrate an idea through the development of a short
p= rogram, there is no requirement or expectation that they do so. Thus, they<= /div>
encompass the notions of theoretical and educational pearls.
Functional Pearls are valued as highly and judged as rigorously a= s ordinary
papers, but using somewhat different criteria. In part= icular, a pearl is not
required to report original research, but,= it should be concise, instructive,
and entertaining. A pearl is = likely to be rejected if its readers get bored, if
the material g= ets too complicated, if too much-specialised knowledge is needed,
or if the writing is inelegant. The key to writing a good pearl is polishi= ng.

A submission that is intended to be treated as a pearl mu= st be marked as such on
the submission web page and should contai= n the words "Functional Pearl"
somewhere in its title o= r subtitle. These steps will alert reviewers to use the
appropria= te evaluation criteria. Pearls will be combined with ordinary papers,
=
however, for the purpose of computing the conference=E2=80=99s accepta= nce rate.

### Experience Reports

The purpose of an Experience R= eport is to describe the experience of using
functional programmi= ng in practice, whether in industrial application, tool
developme= nt, programming education, or any other area.

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

* insights gained from real-world = projects using functional programming
* comparison of functional programming with conventional pr= ogramming in the
context of an industrial project or a universi= ty curriculum
* projec= t-management, business, or legal issues encountered when using
= functional programming in a real-world project
* curricular issues encountered when using functio= nal programming in education
= * real-world constraints that created special challenges for an impl= ementation
of a functional language or for functional programmi= ng in general

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

* Both in the papers and in any citations, the title of eac= h accepted Experience
Report must end with the words "(Exp= erience Report)" in parentheses. The
acceptance rate for E= xperience Reports will be computed and reported
separately from= the rate for ordinary papers.
* Experience Report submissions can be at most 12 pages long, excl= uding
bibliography.
* Each accepted Experience Report will be presented at the confer= ence, but
depending on the number of Experience Reports and reg= ular papers accepted,
authors of Experience Reports may be aske= d to give shorter talks.
* Because the purpose of Experience Reports is to enable our community t= o
understand the application of functional programming, an acce= ptable Experience
Report need not add to the body of knowledge = of the functional-programming
community by presenting novel res= ults or conclusions. It is sufficient if the
report describes a= n illuminating experience with functional programming, or
provi= des evidence for a clear thesis about the use of functional programming.
The experience or thesis must be relevant to ICFP, but it need no= t be novel.

The review committee will accept or reject Experi= ence Reports based on whether
they judge the paper to illuminate = some aspect of the use of functional
programming. Anecdotal evide= nce will be acceptable provided it is well-argued
and the author = explains what efforts were made to gather as much evidence as
pos= sible. Typically, papers that show how functional programming was used are<= /div>
more convincing than papers that say only that functional program= ming was used.
It can be especially effective to present comparis= ons of the situations before
and after the experience described i= n the paper, but other kinds of evidence
would also make sense, d= epending on context. Experience drawn from a single
person=E2=80= =99s experience may be sufficient, but more weight will be given to evidenc= e
drawn from the experience of groups of people.

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

If the pap= er not only describes experience but also presents new technical
= results, or if the experience refutes cherished beliefs of the
fu= nctional-programming community, it may be better to submit it as a full pap= er,
which will be judged by the usual criteria of novelty, origin= ality, and
relevance. The Program Chair will be happy to advise o= n any concerns about which
category to submit to.

<= span style=3D"color:rgb(128,0,0);font-weight:bold">### About PACMPL<= /div>
Proceedings of the ACM on Programming Languages (PACMPL https://pacmpl.acm.org/)
is a = Gold Open Access journal publishing research on all aspects of programming<= /div>
languages, from design to implementation and from mathematical fo= rmalisms to
empirical studies. Each issue of the journal is devot= ed to a particular subject
area within programming languages and = will be announced through publicised Calls
for Papers, like this = one.

### = ICFP Organizers

General Chair:
Ilya Sergey= (NUS)
Program Chair:
Dominique Devriese (KU Leuven)<= /div>
Associate Program Chair:
Peter Thiemann (University o= f Freiburg)
Workshops Co-Chairs:
Ben Greenman (Univer= sity of Utah)
Chandrakana Nandi (Certora)
Artifact Ev= aluation Co-Chairs:
Beno=C3=AEt Montagu (INRIA)
Lio= nel Parreaux (HKUST)
Industrial Relations Chair:
Dani= el Winograd-Cort (Nectry Inc.)
Student Volunteer Chair:
Joe Watt (Institute for Infocomm Research, A*STAR)
SRC Co-Chai= r:
Kuen-Bang Hou (Favonia) (University of Minnesota)
= Publicity Chair:
Sam Westrick (NYU)
Diversity Co-Chai= rs:
Alejandro Russo (Chalmers, DPella)
KC Sivaramak= rishnan (Tarides, IIT Madras)
Web Chair:
Jules Jacobs= (Cornell)
Doctoral Symposium Chair:
Conrad Watt (Nan= yang Technological University)
Programming Contest Organizer:
Liam O'Connor (Australian National University)
SIGPL= AN Conference Manager:
Neringa Young
--0000000000005b34c0062618e04f--