<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<font face="Courier" class=""><br class="">
</font>
<div class=""><font face="Courier" class="">================================================================================</font></div>
<div class=""><font face="Courier" class=""> ACM SIGPLAN CALL FOR SUBMISSIONS</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> Haskell Symposium 2020</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> New Jersey, United States</font></div>
<div class=""><font face="Courier" class=""> 27--28 August, 2020</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> <a href="http://www.haskell.org/haskell-symposium/2020/" class="">
http://www.haskell.org/haskell-symposium/2020/</a></font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">================================================================================</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">The ACM SIGPLAN Haskell Symposium 2020 will be co-located with the 2020</font></div>
<div class=""><font face="Courier" class="">International Conference on Functional Programming (ICFP).</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Like last year, we will be using a lightweight double-blind reviewing process.</font></div>
<div class=""><font face="Courier" class="">See further information below.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">The Haskell Symposium presents original research on Haskell,</font></div>
<div class=""><font face="Courier" class="">discusses practical experience and future development of the language, and</font></div>
<div class=""><font face="Courier" class="">promotes other forms of declarative programming.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Topics of interest include:</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Language design, with a focus on possible extensions and modifications of</font></div>
<div class=""><font face="Courier" class=""> Haskell as well as critical discussions of the status quo;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Theory, such as formal semantics of the present language or future</font></div>
<div class=""><font face="Courier" class=""> extensions, type systems, effects, metatheory, and foundations for</font></div>
<div class=""><font face="Courier" class=""> program analysis and transformation;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Implementations, including program analysis and transformation,</font></div>
<div class=""><font face="Courier" class=""> static and dynamic compilation for sequential, parallel, and distributed</font></div>
<div class=""><font face="Courier" class=""> architectures, memory management, as well as foreign function and</font></div>
<div class=""><font face="Courier" class=""> component interfaces;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Libraries, that demonstrate new ideas or techniques for functional</font></div>
<div class=""><font face="Courier" class=""> programming in Haskell;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Tools, such as profilers, tracers, debuggers, preprocessors,</font></div>
<div class=""><font face="Courier" class=""> and testing tools;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Applications, to scientific and symbolic computing, databases, multimedia,</font></div>
<div class=""><font face="Courier" class=""> telecommunication, the web, and so forth;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Functional Pearls, being elegant and instructive programming examples;</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> * Experience Reports, to document general practice and experience in</font></div>
<div class=""><font face="Courier" class=""> education, industry, or other contexts;</font></div>
<div class=""><font face="Courier" class=""> </font></div>
<div class=""><font face="Courier" class=""> * System Demonstrations, based on running software rather than novel</font></div>
<div class=""><font face="Courier" class=""> research results.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Regular papers should explain their research contributions in both general and</font></div>
<div class=""><font face="Courier" class="">technical terms, identifying what has been accomplished, explaining why it is</font></div>
<div class=""><font face="Courier" class="">significant, and relating it to previous work, and to other languages where</font></div>
<div class=""><font face="Courier" class="">appropriate.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Experience reports and functional pearls need not necessarily report original</font></div>
<div class=""><font face="Courier" class="">academic research results. For example, they may instead report reusable</font></div>
<div class=""><font face="Courier" class="">programming idioms, elegant ways to approach a problem, or practical experience</font></div>
<div class=""><font face="Courier" class="">that will be useful to other users, implementers, or researchers. The key</font></div>
<div class=""><font face="Courier" class="">criterion for such a paper is that it makes a contribution from which other</font></div>
<div class=""><font face="Courier" class="">Haskellers can benefit. It is not enough simply to describe a standard solution</font></div>
<div class=""><font face="Courier" class="">to a standard programming problem, or report on experience where you used</font></div>
<div class=""><font face="Courier" class="">Haskell in the standard way and achieved the result you were expecting.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">System demonstrations should summarize the system capabilities that would be</font></div>
<div class=""><font face="Courier" class="">demonstrated. The proposals will be judged on whether the ensuing session is</font></div>
<div class=""><font face="Courier" class="">likely to be important and interesting to the Haskell community at large,</font></div>
<div class=""><font face="Courier" class="">whether on grounds academic or industrial, theoretical or practical, technical,</font></div>
<div class=""><font face="Courier" class="">social or artistic. Please contact the program chair with any questions about</font></div>
<div class=""><font face="Courier" class="">the relevance of a proposal.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Submission Details</font></div>
<div class=""><font face="Courier" class="">==================</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Early and Regular Track</font></div>
<div class=""><font face="Courier" class="">-----------------------</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">The Haskell Symposium uses a two-track submission process so that some papers</font></div>
<div class=""><font face="Courier" class="">can gain early feedback. Strong papers submitted to the early track are</font></div>
<div class=""><font face="Courier" class="">accepted outright, and the others will be given their reviews and invited to</font></div>
<div class=""><font face="Courier" class="">resubmit to the regular track. Papers accepted via the early and regular</font></div>
<div class=""><font face="Courier" class="">tracks are considered of equal value and will not be distinguished in the</font></div>
<div class=""><font face="Courier" class="">proceedings. Although all papers may be submitted to the early track, authors</font></div>
<div class=""><font face="Courier" class="">of functional pearls and experience reports are particularly encouraged to use</font></div>
<div class=""><font face="Courier" class="">this mechanism. The success of these papers depends heavily on the way they</font></div>
<div class=""><font face="Courier" class="">are presented, and submitting early will give the program committee a chance</font></div>
<div class=""><font face="Courier" class="">to provide feedback and help draw out the key ideas.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Formatting</font></div>
<div class=""><font face="Courier" class="">----------</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Submitted papers should be in portable document format (PDF), formatted using</font></div>
<div class=""><font face="Courier" class="">the ACM SIGPLAN style guidelines. Authors should use the `acmart` format, with</font></div>
<div class=""><font face="Courier" class="">the `sigplan` sub-format for ACM proceedings. For details, see:</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> <a href="http://www.sigplan.org/Resources/Author/#acmart-format" class="">
http://www.sigplan.org/Resources/Author/#acmart-format</a></font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">It is recommended to use the `review` option when submitting a paper; this option</font></div>
<div class=""><font face="Courier" class="">enables line numbers for easy reference in reviews.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Functional pearls, experience reports, and demo proposals should be</font></div>
<div class=""><font face="Courier" class="">labelled clearly as such.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Lightweight Double-blind Reviewing</font></div>
<div class=""><font face="Courier" class="">----------------------------------</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Haskell Symposium 2020 will use a lightweight double-blind reviewing process.</font></div>
<div class=""><font face="Courier" class="">To facilitate this, submitted papers must adhere to two rules:</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> 1. Author names and institutions must be omitted, and</font></div>
<div class=""><font face="Courier" class=""> 2. References to authors’ own related work should be in the third person</font></div>
<div class=""><font face="Courier" class=""> (e.g., not “We build on our previous work …” but rather “We build on the work of …”).</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">The purpose of this process is to help the reviewers come to an initial</font></div>
<div class=""><font face="Courier" class="">judgment about the paper without bias, not to make it impossible for them to</font></div>
<div class=""><font face="Courier" class="">discover the authors if they were to try. Nothing should be done in the name</font></div>
<div class=""><font face="Courier" class="">of anonymity that weakens the submission or makes the job of reviewing the</font></div>
<div class=""><font face="Courier" class="">paper more difficult (e.g., important background references should not be</font></div>
<div class=""><font face="Courier" class="">omitted or anonymized). In addition, authors should feel free to disseminate</font></div>
<div class=""><font face="Courier" class="">their ideas or draft versions of their paper as they normally would. For</font></div>
<div class=""><font face="Courier" class="">instance, authors may post drafts of their papers on the web or give talks on</font></div>
<div class=""><font face="Courier" class="">their research ideas.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">A reviewer will learn the identity of the author(s) of a paper after a review</font></div>
<div class=""><font face="Courier" class="">is submitted.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Page Limits</font></div>
<div class=""><font face="Courier" class="">-----------</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">The length of submissions should not exceed the following limits:</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Regular paper: 12 pages</font></div>
<div class=""><font face="Courier" class="">Functional pearl: 12 pages</font></div>
<div class=""><font face="Courier" class="">Experience report: 6 pages</font></div>
<div class=""><font face="Courier" class="">Demo proposal: 2 pages</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">There is no requirement that all pages are used. For example, a</font></div>
<div class=""><font face="Courier" class="">functional pearl may be much shorter than 12 pages. In all cases,</font></div>
<div class=""><font face="Courier" class="">the list of references is not counted against these page limits.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Deadlines</font></div>
<div class=""><font face="Courier" class="">---------</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Early track:</font></div>
<div class=""><font face="Courier" class=""> Submission deadline: 20 March 2020 (Fri)</font></div>
<div class=""><font face="Courier" class=""> Notification: 24 April 2020 (Fri)</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Regular track and demos:</font></div>
<div class=""><font face="Courier" class=""> Submission deadline: 15 May 2020 (Fri)</font></div>
<div class=""><font face="Courier" class=""> Notification: 26 June 2020 (Fri)</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Deadlines are valid anywhere on Earth.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Submission</font></div>
<div class=""><font face="Courier" class="">----------</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Submissions must adhere to SIGPLAN's republication policy</font></div>
<div class=""><font face="Courier" class="">(<a href="http://sigplan.org/Resources/Policies/Republication/" class="">http://sigplan.org/Resources/Policies/Republication/</a>), and authors</font></div>
<div class=""><font face="Courier" class="">should be aware of ACM's policies on plagiarism</font></div>
<div class=""><font face="Courier" class="">(<a href="https://www.acm.org/publications/policies/plagiarism" class="">https://www.acm.org/publications/policies/plagiarism</a>).</font></div>
<div class=""><font face="Courier" class="">Program Committee members are allowed to submit papers, but their papers will</font></div>
<div class=""><font face="Courier" class="">be held to a higher standard.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">The paper submission deadline and length limitations are firm.</font></div>
<div class=""><font face="Courier" class="">There will be no extensions, and papers violating the length</font></div>
<div class=""><font face="Courier" class="">limitations will be summarily rejected.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Papers should be submitted through HotCRP at:</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class=""> <a href="https://haskell20.hotcrp.com/" class="">
https://haskell20.hotcrp.com/</a></font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Improved versions of a paper may be submitted at any point before the</font></div>
<div class=""><font face="Courier" class="">submission deadline using the same web interface.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Supplementary material: Authors have the option to attach supplementary</font></div>
<div class=""><font face="Courier" class="">material to a submission, on the understanding that reviewers may choose not</font></div>
<div class=""><font face="Courier" class="">to look at it. This supplementary material should not be submitted as part of</font></div>
<div class=""><font face="Courier" class="">the main document; instead, it should be uploaded as a separate PDF document</font></div>
<div class=""><font face="Courier" class="">or tarball.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Supplementary material should be uploaded at submission time, not by providing</font></div>
<div class=""><font face="Courier" class="">a URL in the paper that points to an external repository.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Authors are free to upload both anonymized and non-anonymized supplementary</font></div>
<div class=""><font face="Courier" class="">material. Anonymized supplementary material will be visible to reviewers</font></div>
<div class=""><font face="Courier" class="">immediately; non-anonymized supplementary material will be revealed to</font></div>
<div class=""><font face="Courier" class="">reviewers only after they have submitted their review of the paper and learned</font></div>
<div class=""><font face="Courier" class="">the identity of the author(s).</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Resubmitted Papers: Authors who submit a revised version of a paper that has</font></div>
<div class=""><font face="Courier" class="">previously been rejected by another conference have the option to attach an</font></div>
<div class=""><font face="Courier" class="">annotated copy of the reviews of their previous submission(s), explaining how</font></div>
<div class=""><font face="Courier" class="">they have addressed these previous reviews in the present submission. If a</font></div>
<div class=""><font face="Courier" class="">reviewer identifies him/herself as a reviewer of this previous submission and</font></div>
<div class=""><font face="Courier" class="">wishes to see how his/her comments have been addressed, the principal editor</font></div>
<div class=""><font face="Courier" class="">will communicate to this reviewer the annotated copy of his/her previous</font></div>
<div class=""><font face="Courier" class="">review. Otherwise, no reviewer will read the annotated copies of the previous</font></div>
<div class=""><font face="Courier" class="">reviews.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Travel Support</font></div>
<div class=""><font face="Courier" class="">==============</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Student attendees with accepted papers can apply for a SIGPLAN PAC grant to</font></div>
<div class=""><font face="Courier" class="">help cover travel expenses. PAC also offers other support, such as for</font></div>
<div class=""><font face="Courier" class="">child-care expenses during the meeting or for travel costs for companions of</font></div>
<div class=""><font face="Courier" class="">SIGPLAN members with physical disabilities, as well as for travel from</font></div>
<div class=""><font face="Courier" class="">locations outside of North America and Europe. For details on the PAC program,</font></div>
<div class=""><font face="Courier" class="">see its web page (<a href="http://pac.sigplan.org" class="">http://pac.sigplan.org</a>).</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Proceedings</font></div>
<div class=""><font face="Courier" class="">===========</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Accepted papers will be included in the ACM Digital Library. Their authors </font></div>
<div class=""><font face="Courier" class="">will be required to choose one of the following options:</font></div>
<div class=""><font face="Courier" class="">- Author retains copyright of the work and grants ACM a non-exclusive</font></div>
<div class=""><font face="Courier" class=""> permission-to-publish license (and, optionally, licenses the work with a</font></div>
<div class=""><font face="Courier" class=""> Creative Commons license); </font></div>
<div class=""><font face="Courier" class="">- Author retains copyright of the work and grants ACM an exclusive</font></div>
<div class=""><font face="Courier" class=""> permssion-to-publish license; </font></div>
<div class=""><font face="Courier" class="">- Author transfers copyright of the work to ACM. </font></div>
<div class=""><font face="Courier" class="">For more information, please see ACM Copyright Policy</font></div>
<div class=""><font face="Courier" class="">(<a href="http://www.acm.org/publications/policies/copyright-policy" class="">http://www.acm.org/publications/policies/copyright-policy</a>) and ACM Author</font></div>
<div class=""><font face="Courier" class="">Rights (<a href="http://authors.acm.org/main.html" class="">http://authors.acm.org/main.html</a>).</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Accepted proposals for system demonstrations will be posted on the</font></div>
<div class=""><font face="Courier" class="">symposium website but not formally published in the proceedings.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Publication date: The official publication date of accepted papers is</font></div>
<div class=""><font face="Courier" class="">the date the proceedings are made available in the ACM Digital</font></div>
<div class=""><font face="Courier" class="">Library. This date may be up to two weeks prior to the first day of the</font></div>
<div class=""><font face="Courier" class="">conference. The official publication date affects the deadline for any</font></div>
<div class=""><font face="Courier" class="">patent filings related to published work.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Artifacts</font></div>
<div class=""><font face="Courier" class="">=========</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Authors of accepted papers are encouraged to make auxiliary material (artifacts</font></div>
<div class=""><font face="Courier" class="">like source code, test data, etc.) available with their paper. They can opt to</font></div>
<div class=""><font face="Courier" class="">have these artifacts published alongside their paper in the ACM Digital Library</font></div>
<div class=""><font face="Courier" class="">(copyright of artifacts remains with the authors).</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">If an accepted paper's artifacts are made permanently available for retrieval in a</font></div>
<div class=""><font face="Courier" class="">publicly accessible archival repository like the ACM Digital Library, that paper</font></div>
<div class=""><font face="Courier" class="">qualifies for an Artifacts Available badge</font></div>
<div class=""><font face="Courier" class="">(<a href="https://www.acm.org/publications/policies/artifact-review-badging#available" class="">https://www.acm.org/publications/policies/artifact-review-badging#available</a>).</font></div>
<div class=""><font face="Courier" class="">Applications for such a badge can be made after paper acceptance and will be</font></div>
<div class=""><font face="Courier" class="">reviewed by the PC chair.</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Program Committee</font></div>
<div class=""><font face="Courier" class="">=================</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">Arthur Azevedo de Amorim<span class="Apple-tab-span" style="white-space:pre">
</span>Carnegie Mellon University</font></div>
<div class=""><font face="Courier" class="">Manuel Chakravarty<span class="Apple-tab-span" style="white-space:pre">
</span>Tweag I/O / IOHK</font></div>
<div class=""><font face="Courier" class="">Jan Christiansen<span class="Apple-tab-span" style="white-space:pre">
</span>Flensburg University of Applied Sciences</font></div>
<div class=""><font face="Courier" class="">Youyou Cong<span class="Apple-tab-span" style="white-space:pre">
</span>Tokyo Institute of Technology</font></div>
<div class=""><font face="Courier" class="">Pierre-Evariste Dagand<span class="Apple-tab-span" style="white-space:pre">
</span>CNRS</font></div>
<div class=""><font face="Courier" class="">Anton Ekblad<span class="Apple-tab-span" style="white-space:pre">
</span>Chalmers University of Technology</font></div>
<div class=""><font face="Courier" class="">Jurriaan Hage<span class="Apple-tab-span" style="white-space:pre">
</span>Universiteit Utrecht</font></div>
<div class=""><font face="Courier" class="">Graham Hutton<span class="Apple-tab-span" style="white-space:pre">
</span>University of Nottingham</font></div>
<div class=""><font face="Courier" class="">José Pedro Magalhães<span class="Apple-tab-span" style="white-space:pre">
</span>Standard Chartered</font></div>
<div class=""><font face="Courier" class="">Clare Martin<span class="Apple-tab-span" style="white-space:pre">
</span>Oxford Brookes University</font></div>
<div class=""><font face="Courier" class="">Andrey Mokhov<span class="Apple-tab-span" style="white-space:pre">
</span>Jane Street </font></div>
<div class=""><font face="Courier" class="">Shin-Cheng Mu<span class="Apple-tab-span" style="white-space:pre">
</span>Academia Sinica</font></div>
<div class=""><font face="Courier" class="">Nikolaos Papaspyrou<span class="Apple-tab-span" style="white-space:pre">
</span>National Technical University of Athens</font></div>
<div class=""><font face="Courier" class="">Simon Peyton Jones<span class="Apple-tab-span" style="white-space:pre">
</span>Microsoft Research Cambridge</font></div>
<div class=""><font face="Courier" class="">Norman Ramsey<span class="Apple-tab-span" style="white-space:pre">
</span>Tufts University</font></div>
<div class=""><font face="Courier" class="">Exequiel Rivas<span class="Apple-tab-span" style="white-space:pre">
</span>INRIA</font></div>
<div class=""><font face="Courier" class="">Tom Schrijvers (chair)<span class="Apple-tab-span" style="white-space:pre">
</span>KU Leuven</font></div>
<div class=""><font face="Courier" class="">Martin Sulzmann<span class="Apple-tab-span" style="white-space:pre">
</span>Karlsruhe University of Applied Sciences</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">If you have questions, please contact the chair at:
<a href="mailto:tom.schrijvers@kuleuven.be" class="">tom.schrijvers@kuleuven.be</a></font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">================================================================================</font></div>
<div class=""><br class="">
</div>
</body>
</html>