Accepted Papers

Attending PLDI

PLDI 2023 is co-located with FCRC 2023.

Hotel:

PLDI will be held at the Orlando World Center Marriott. You may book a room at the ACM rate by visiting the following FCRC page.

The deadline for reserving a room at the discounted ACM rate is May 15.

Registration:

Registration will be handled through FCRC 2023. Be sure to register for PLDI 2023 during registration. You may register here.

Call for Previously Un-presented SIGPLAN Paper Presentations

PLDI’23 will continue the tradition of allowing previously un-presented work from ICFP, POPL, and OOPSLA to be presented at PLDI. This mechanism is designed to provide an opportunity to authors who, for reasons beyond their control, could not present at the venue in which their work was accepted, and would like the opportunity to present to an audience at PLDI.

Please note that unfortunately there will be limited spots available due to the space constraints at the venue, so there is no guarantee that we will be able to accept your work for presentation at PLDI’23. We will announce decisions no later than Monday April 3, 2023.

Please use the form below to inform us of your desire to present your work at PLDI’23.

https://forms.gle/AZtKMwDNycDnWwvi9

Call for Papers

PACMPL Issue PLDI 2023 seeks contributions on all aspects of programming languages research, broadly construed, including design, implementation, theory, applications, and performance. Authors of papers published in PACMPL Issue PLDI 2023 will be invited to present their work in the PLDI conference in June 2023, which is sponsored by ACM SIGPLAN.

Scope

PLDI is a premier forum for programming language research, broadly construed. Outstanding research that extends and/or applies programming-language concepts to advance the field of computing is welcome. Novel system designs, thorough empirical work, well-motivated theoretical results, and new application areas are all in scope for PLDI.

Evaluation Criteria and Process

Reviewers will evaluate submissions for accuracy, significance, originality, and clarity. Submissions should be organized to communicate clearly to a broad programming-language audience as well as experts on the paper’s topics. Papers should identify what has been accomplished and how it relates to previous work. Authors of empirical papers are encouraged to consider the seven categories of the SIGPLAN Empirical Evaluation Guidelines when preparing submissions.

To conform with ACM requirements for journal publication, the selection of papers will be made in two rounds of reviewing. In the first round, reviewers will assesses the papers according to the quality criteria listed above. Authors will be given several days to compose a written response to the reviews received in the first round—e.g., to correct errors and clarify technical concerns. At the end of the first round, the Review Committee will conditionally accept a subset of the submissions and all other submissions will be rejected. In the second round, authors of conditionally-accepted papers will be given an opportunity to improve specific aspects of the research and the paper, as identified by the reviewers. Authors will have sufficient time to perform the required revisions and re-submit the paper. The same reviewers as in the first round will then assess how the revision requests have been acted upon by the authors. Revisions that fail to adequately address the reviewers’ original concerns will result in rejection.

The Review Committee will make final decisions regarding (conditional) acceptance and rejection, although reviews for a given paper will typically be performed by a subset of the committee. Authors may only contact the Associate Editor about submitted papers during the review period. Contacting Review Committee members about submitted paper(s) is an ethical violation and may be grounds for summary rejection.

Deadlines and formatting requirements, detailed below, will be strictly enforced, with extremely rare extenuating circumstances considered at the discretion of the Associate Editor.

Double-Blind Reviewing

Consistent with double-blind reviewing, author names and affiliations must be omitted from the submission. If the submission refers to prior work done by the authors, that reference should be made in third person. Any supplementary material must also be anonymized. These are firm submission requirements. The Review Committee will only learn the identities of authors of accepted papers following the second round of reviewing.

The FAQ on Double-Blind Reviewing clarifies the policy for the most common scenarios. But there are many gray areas and trade-offs. If you have any doubts about how to interpret the double-blind rules, or any cases that are not fully covered by the FAQ, please contact the Associate Editor. In complex cases, it is better to get guidance from the Associate Editor than to risk summary rejection.

Submission Site Information

The submission site is https://pldi2023.hotcrp.com.

Authors can submit multiple times prior to the (firm!) deadline. Only the last submission will be reviewed. There is no abstract deadline. The submission site requires entering author names and affiliations, relevant topics, and potential conflicts. Addition or removal of authors after the submission deadline will need to be approved by the Associate Editor (as this kind of change potentially undermines the goal of eliminating conflicts during paper assignment).

The submission deadline is 11:59PM November 10, 2022 anywhere on earth: https://en.wikipedia.org/wiki/Anywhere_on_Earth

Declaring Conflicts

When submitting the paper, you will need to declare potential conflicts. Conflicts should be declared between an adviser and an advisee (e.g., Ph.D., post-doc). Other conflicts include institutional conflicts, financial conflicts of interest, friends or relatives, or any recent co-authors on papers and proposals (last 2 years).

Please do not declare spurious conflicts: such incorrect conflicts are especially harmful if the aim is to subvert the normal peer-review process by excluding potential reviewers. Listing spurious conflicts can be grounds for rejection. If you are unsure about whether or not a given relationship constitutes a conflict, please consult the Associate Editor.

Formatting Requirements

Each paper should have no more than 20 pages of text, excluding bibliography, using the ACM Proceedings format. This format is chosen for compatibility with PACMPL. It is a single-column page layout with a 10 pt font, 12 pt line spacing, and wider margins than recent PLDI page layouts. In this format, the main text block is 5.478 in (13.91 cm) wide and 7.884 in (20.03 cm) tall. Use of a different format (e.g., smaller fonts or a larger text block) is grounds for summary rejection. PACMPL templates for Microsoft Word and LaTeX can be found at the SIGPLAN author information page. Authors using LaTeX should use the sample-acmsmall-conf.tex file (found in the samples folder of the acmart package) with the acmsmall option. We also strongly encourage use of the review and screen options as well. Papers may be submmitted using numeric citations, but final versions of accepted papers must use author-year format for citations. Submissions should be in PDF and printable on both US Letter and A4 paper. Please take care to ensure that figures and tables are legible, even when the paper is printed in gray-scale. Papers that exceed the length requirement, deviate from the expected format, or are submitted late will be rejected.

Supplementary Material

Authors are welcome to provide supplementary material if that material supports the claims in the paper. Such material may include proofs, experimental results, and/or data sets. This material should be uploaded at the same time as the submission. Reviewers are not required to examine the supplementary material but may refer to it if they would like to find further evidence supporting the claims in the paper.

Plagiarism and Concurrent Work

Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by the SIGPLAN Republication Policy and ACM Policy on Plagiarism. Concurrent submissions to other conferences, workshops, journals, or similar venues of publication are disallowed. Prior work must, as always, be cited and referred to in the third person even if it is the authors’ work, so as to preserve author anonymity. If you have further questions, please contact the Associate Editor.

Artifact Evaluation for Accepted Papers

Authors of accepted papers will be invited to submit supporting materials to the Artifact Evaluation process. Artifact Evaluation is run by a separate committee whose task is to assess how well the artifacts support the work described in the papers. This submission is voluntary but encouraged and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully will receive a badge printed on the papers themselves. Authors of accepted papers are encouraged to make these materials publicly available upon publication of the proceedings, by including them as “source materials” in the ACM Digital Library.

Open Access and Copyright

As a Gold Open Access journal, PACMPL is committed to making peer-reviewed scientific research free of restrictions on both access and (re-)use. Authors are strongly encouraged to support liberal open access by licensing their work with the Creative Commons Attribution 4.0 International (CC BY) license, which grants readers (re-)use rights.

Authors of accepted papers will be required to provide an ORCID for each co-author and choose one of the following publication rights:

• Author licenses the work with a Creative Commons license, retains copyright, and (implicitly) grants ACM non-exclusive permission to publish (suggested choice).
• Author retains copyright of the work and grants ACM a non-exclusive permission to publish license.
• Author retains copyright of the work and grants ACM an exclusive permission to publish license.
• Author transfers copyright of the work to ACM.

These choices follow from ACM Copyright Policy and ACM Author Rights, corresponding to ACM’s “author pays” option. While PACMPL may ask authors who have funding for open-access fees to voluntarily cover the article processing charge (currently, US$400), payment is not required for publication. PACMPL and SIGPLAN continue to explore the best models for funding open access, focusing on approaches that are sustainable in the long-term while reducing short-term risk.

Publication Date

All papers will be archived by the ACM Digital Library. Authors will have the option of including supplementary material with their paper. The official publication date is the date the proceedings are made available in the ACM Digital Library or the first day of the conference, which ever is sooner. Note that the date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work.

Presentations

Authors of accepted papers will be invited to present their work at PLDI. Authors who need financial assistance for travel to the conferences should apply for a grant from the SIGPLAN Professional Activities Committee (PAC) program. We welcome all authors, regardless of nationality. If authors are to obtain visas to travel to the conference despite making reasonable effort, we will make arrangements to facilitate remote participation or presentation by another attendee on behalf of the authors.

Distinguished Paper Awards

Up to 10% of the accepted papers may be designated as Distinguished Papers. This award highlights papers that the Review Committee believes should be read by a broad audience due to their relevance, originality, significance, and clarity. The set of distinguished papers will be chosen through a rigorous review process of the final papers, carried out by a subset of the Review Committee.

Acknowledgments

This call-for-papers is an adaptation and evolution of content from previous SIGPLAN conferences. We are grateful to prior organizers for their work, which is reused here.

General

Q: Why are you using double-blind reviewing?

A: Studies have shown that a reviewer’s attitude toward a submission may be affected, even unconsciously, by the identity of the authors. We want reviewers to be able to approach each submission without any such, possibly involuntary, pre-judgment. Many computer science publications have embraced double-blind reviewing. PLDI has used it for several years now and doing so is stipulated in the [Practices of PLDI](Practices of PLDI).

Q: Do you really think blinding actually works? I suspect reviewers can often guess who the authors are anyway.

A: It is rare for authorship to be guessed correctly, even by expert reviewers, as detailed in this study.

Q: Couldn’t blind submission create an injustice where a paper is inappropriately rejected based upon supposedly-prior work which was actually by the same authors and not previously published?

A: Reviewers are held accountable for their positions and are required to identify any supposed prior work that they believe undermines the novelty of the paper. Any assertion that “this has been done before” by reviewers should be supported with concrete information. The author response mechanism exists in part to hold reviewers accountable for claims that may be incorrect.

For authors

Q: What exactly do I have to do to anonymize my paper?

A: Use common sense. Your job is not to make your identity undiscoverable but simply to make it possible for reviewers to evaluate your submission without having to know who you are. The specific guidelines stated in the call for papers are simple: omit authors’ names from your title page, and when you cite your own work, refer to it in the third person. For example, if your name is Smith and you have worked on amphibious type systems, instead of saying “We extend our earlier work on statically typed toads [Smith 2004],” you might say “We extend Smith’s [2004] earlier work on statically typed toads.” Also, be sure not to include any acknowledgements that would give away your identity. In general, you should aim to reduce the risk of accidental unblinding. For example, if your paper is the first to describe a system with a well-known name or codename, or you use a personally-identifiable naming convention for your work, then use a different name for your submission (which you may indicate has been changed for the purposes of double-blind reviewing). You should also avoid revealing the institutional affiliation of authors or at which the work was performed.

Q: I would like to provide supplementary material for consideration, e.g., the code of my implementation or proofs of theorems. How do I do this?

A (and also see the next question): On the submission site there will be an option to submit supplementary material along with your main paper. This supplementary material should also be anonymized; it may be viewed by reviewers during the review period, so it should adhere to the same double-blind guidelines.

Q: My submission is based on code available in a public repository. How do I deal with this?

A: Making your code publicly available is not incompatible with double-blind reviewing. You should do the following. First, cite the code in your paper, but remove the actual URL and, instead say “link to repository removed for double-blind review” or similar. Second, if, when writing your author response, you believe reviewer access to your code would help, say so in your author response (without providing the URL), and upload a zip file containing the code under supplemental materials (but make sure that the code/documentation does not reveal the identity of the authors).

Q: I am building on my own past work on the WizWoz system. Do I need to rename this system in my paper for purposes of anonymity, so as to remove the implied connection between my authorship of past work on this system and my present submission?

A: Maybe. The core question is really whether the system is one that, once identified, automatically identifies the author(s) and/or the institution. If the system is widely available, and especially if it has a substantial body of contributors and has been out for a while, then these conditions may not hold (e.g., LLVM or HotSpot), because there would be considerable doubt about authorship. By contrast, a paper on a modification to a proprietary system (e.g., Visual C++, or a research project that has not open-sourced its code) implicitly reveals the identity of the authors or their institution. If naming your system essentially reveals your identity (or institution), then anonymize it. In your submission, point out that the system name has been anonymized. If you have any doubts, please contact the Associate Editor.

Q: I am submitting a paper that extends my own work that previously appeared at a workshop. Should I anonymize any reference to that prior work?

A: No. But we recommend you do not use the same title for your submission, so that it is clearly distinguished from the prior paper. In general, there is rarely a good reason to anonymize a citation. One possibility is for work that is tightly related to the present submission and is also under review. When in doubt, contact the Associate Editor.

Q: Am I allowed to post my (non-blinded) paper on my web page? Can I advertise the unblinded version of my paper on mailing lists or send it to colleagues? Can I give a talk about my work while it is under review? How do I handle social media? What about arXiv?

A: We have developed guidelines, described here, to help everyone navigate in the same way the tension between the normal communication of scientific results, which double-blind reviewing should not impede, and actions that essentially force potential reviewers to learn the identity of the authors for a submission. Roughly speaking, you may (of course!) discuss work under submission, but you should not broadly advertise your work through media that is likely to reach your reviewers. We acknowledge there are gray areas and trade-offs; we cannot describe every possible scenario.

Things you may do:

• Put your submission on your home page.
• Discuss your work with anyone who is not on the Review Committee, or with people on the committees with whom you already have a conflict.
• Present your work at professional meetings, job interviews, etc.
• Submit work previously discussed at an informal workshop, previously posted on arXiv or a similar site, previously submitted to a conference not using double-blind reviewing, etc.

Things you should not do:

• Contact members of the Review Committee about your work, or deliberately present your work where you expect them to be.
• Publicize your work on major mailing lists used by the community (because potential reviewers likely read these lists).
• Publicize your work on social media if wide public [re-]propagation is common (e.g., Twitter) and therefore likely to reach potential reviewers. For example, on Facebook, a post with a broad privacy setting (public or all friends) saying, “Whew, PLDI paper in, time to sleep” is okay, but one describing the work or giving its title is not appropriate. Alternatively, a post to a group including only the colleagues at your institution is fine. Reviewers will not be asked to recuse themselves from reviewing your paper unless they feel you have gone out of your way to advertise your authorship information to them. If you are unsure about what constitutes “going out of your way”, please contact the Associate Editor.

Q: Will the fact that PLDI is double-blind have an impact on handling conflicts-of-interest?

A: Double-blind reviewing does not change the principle that reviewers should not review papers with which they have a conflict of interest, even if they do not immediately know who the authors are. Authors declare conflicts-of-interest when submitting their papers using the guidelines in the call-for-papers. Papers will not be assigned to reviewers who have a conflict.

For reviewers

Q: What should I do if I learn the authors’ identity? What should I do if a prospective author contacts me and asks to visit my institution?

A: If you feel that the authors’ actions are largely aimed at ensuring that potential reviewers know their identity, contact the Associate Editor. Otherwise, you should not treat double-blind reviewing differently from other reviewing. In particular, refrain from seeking out information on the authors’ identity, but if you discover it accidentally this will not automatically disqualify you as a reviewer. Use your best judgment.

Q: If I am assigned a paper for which I feel I am not an expert, how do I seek an outside review?

A: PC members should write their own reviews and not delegate them to someone else. If doing so is problematic for some papers (e.g., you do not feel completely qualified), then please take the following steps: First, submit a review for your paper that is as careful as possible, outlining areas where you think your knowledge is lacking. Assuming we have sufficient expert reviews, that could be the end of it: non-expert reviews are valuable too, since conference attendees are by-and-large not experts for any given paper. Second, the review form provides a mechanism for suggesting additional expert reviewers to the PC Chair, who may contact them if additional expertise is needed. Please do not contact outside reviewers yourself.

Q: How do we handle potential conflicts of interest since I cannot see the author names?

A: The conference review system will ask that you identify conflicts of interest when you get an account on the submission system. Feel free to also identify additional authors whose papers you feel you could not review fairly for reasons other than those given (e.g., strong personal friendship).

Q: How should I avoid learning the authors’ identity if I am using web-search in the process of performing my review?

A: You should make a good-faith effort not to find the authors’ identity during the review period, but if you inadvertently do so, this does not disqualify you from reviewing the paper. As part of the good-faith effort, do not use search engines with terms like the paper’s title or the name of a new system being discussed. If you need to search for related work you believe exists, do so after completing a preliminary review of the paper.

Q: When will author identities be revealed?

A: The Review Committee will only learn the identities of authors of accepted papers following the second round of reviewing. The authors of rejected papers will remain anonymous to everyone except the Associate Editor.

PLDI’23 Speaker’s Guide

This document is for those presenting a paper at PLDI’23. There are separate guides for ISMM, LCTES, and PLDI workshop speakers.

Congratulations on having your paper accepted at PLDI’23! This document will help ensure your presentation runs smoothly and has the best possible audience impact. Please read it in its entirety.

Checklist

Before PLDI:

• Prepare and practice.
• Ensure your talk runs for no more than 15 minutes.
• Sign up for Discord (details here).
• Upload a backup copy of your talk slides (follow steps listed below).
• Check the program to establish when and where your talk will be.
• Ensure you have a HDMI adaptor for your device.

Before your talk:

• Familiarize yourself with the room you will be speaking in.
• Find and introduce yourself to your session chair.
• Find the Discord channel for your session, so you can monitor questions.
• Attend the mandatory video check before your session (details below).
• Ensure that you are in the room no later than 5 minutes before the start of your session.

After your talk:

• Expect questions from the floor and session chair.
• Once you’ve completed your talk and Q&A, monitor Discord for follow-up questions.

Preparing Your Talk

Your work will have a greater impact if you’re well prepared.

It is very important that you run to schedule. The PLDI’23 schedule is extremely tight, with hard stops imposed by FCRC scheduling. Session chairs have been asked to stick rigidly to the schedule.

Guidelines

1. Your talk should run for no more than 15 minutes , uninterrupted. This gives you about four minutes for questions and one minute for speaker change-over.
2. Your talk should be prepared for the standard 16:9 widescreen ratio. If your talk is in a different ratio, at best it will be pillarboxed, wasting screen real estate and diminishing impact, and at worst, it won’t display correctly.
3. You will present your talk from a lectern, using a fixed lectern mic.
4. You should provide a backup copy of your slides ahead of time in either pdf or powerpoint.
5. If you have an embedded video in your presentation, please inform the video team during your mandatory video check before your session.

Uploading Your Presentation

As an insurance against technical failures, we ask all speakers to make a backup copy of their presentation available to the video team by uploading it the day before the session. You’re welcome to upload fresh copies at any time.

• Format: your presentation must be saved as a powerpoint or pdf file (sorry!)
• Naming: you must use your paper ID as your file name (e.g. <pldi paper ID>.[ppt,pptx,pdf])
• Location: please use this link: https://bit.ly/pldi23upload

This requirement gives you assurance that if some major technical problem were to arise (such as a failure of your laptop), you will still be able to give your talk. If you do not make your presentation available in advance, and significant technical problems arise, we may have to shorten your presentation to keep to our tight schedule.

The requirement for you to use pdf or powerpoint for your backup copy is a pragmatic tradeoff. These slides will only be used in case of a technical emergency. We want to have the highest possible assurance that they will work without fuss on a third party device should such an emergency occur. If you use Google slides, Keynote, or some other software, please use the export feature to create either powerpoint or pdf backups.

If you elect not to upload a backup copy, please understand that this limits our volunteers’ capacity to assist you if a technical problem arises when you give your presentation.

Advice

There are many excellent sources of advice on giving good talks, including from Simon Peyton Jones, Michael Hicks, Michael Ernst, Ranjit Jhala, and Derek Dreyer. Make good use of these!

Mandatory Video Check

All speakers are required to be in the room and check in with their session chair and the video team no later than 5 minutes before their session starts. You will need to plug a HDMI cord into your device. Please bring your own HDMI adapter, if required. Please note that due to our very tight schedule, speakers who fail to upload their talk in advance and/or fail to attend the video check 5 minutes before their session may have their talk cut short if technical issues arise.

Q&A

If you stick to the above schedule you will have about 4 minutes for questions. The in-room audience will be able to ask questions via a queue at a single microphone on a stand in the center of the room. In-room attendees and remote attendees will also be able to ask questions via Discord. Your session chair will monitor questions on Discord and might ask questions as they see them appearing there.

It is good practice, as the speaker, to repeat your understanding of the question before providing your answer. This is particularly important when time is tight because it reduces opportunities for time being wasted on account of a misunderstanding.

Once your talk is finished, please go on to Discord and respond to any questions or follow-up questions that appear there.

Remote Audience

Your talk will be streamed to Discord and YouTube with live captioning. Your remote audience will be able to write questions in the Discord channel created for your session (they won’t be able to ask questions via audio or video). They should see your slides, a video feed of you speaking, and live captions. As mentioned above, your session chair may relay questions from Discord.

Remote Presenters

If it isn’t possible for any of the authors to attend PLDI in person, you will need to have informed the program chair well in advance, and they will make special arrangements for you to present remotely.

The following notes apply only to those who have received permission from the program chair to present remotely. You should have been in direct contact with the PLDI video team on Discord.

Discord

We will use Discord as the virtual platform for this conference. You should familiarize yourself with Discord as an audience member well before your talk. We will use it for: a) the remote audience, b) delivery of remote talks, and c) communicating logistics.

If you are a remote speaker, 15 minutes before your talk, you should go to the voice channel #speakers-queue and wait to receive the Presenter role. With that, you’ll be able to see a private channel. Once that happens, share your screen and wait for the sign to start the presentation.

If you don’t receive the role, send a private message to Hanneli and let her know you are presenting shortly.

Connectivity

Please do the best you can to ensure that you have good connectivity at the time of your presentation. To protect against the possibility of a major technical failure, we encourage you to record a 15 minute video version of your talk, and share it with the video team well before your talk (see notes above for sharing slides). The video team can then use your video as a back-up in case of a major problem.

Limitations

Remote speakers should take care before including embedded audio in their talk. While this is possible, it can be difficult. If you need to do this, please consult directly with the video team and have it tested well in advance.

Q&A

Your session chair will introduce you and field questions just as for in-person sessions. You do not need to monitor Discord during your talk. Your Q&A will involve answering questions verbally, just as for in-person talks, only you’ll do so via video. As with in-person sessions, timing is very tight, so please be sure to stick to your 15 minute speaking time, or risk losing your Q&A time. You can respond to follow-up questions online after your talk has finished.

Thank you for agreeing to serve as a session chair at PLDI ’23! Here are some basic instructions for session chairs to help everything run smoothly.

Well before your session…

• Install Discord and familiarize yourself with the PLDI discord server and join the channel for your session.
• Skim each paper in your session and come up with at least one question to ask during Q&A in case the audience doesn’t have any.
• Consult the list of PLDI Speakers and contact each speaker. Ask them for guidance on name pronunciation and any other details they think might be important for introducing them. Also remind them find you in the break before the session to introduce themselves to you and do the mandatory A/V check.
• If any talk in your session is being given remotely, contact the video team (Guilherme Espada, John Zhuang Hui, and Zixian Cai), for further instructions via the #video-chairs Discord channel

In the break just before your session…

• Go to the meeting room at least 30 minutes before the session.
• Introduce yourself to the A/V chairs and the student volunteers.
• Familiarize yourself with the layout and arrangement of the meeting room.
• Confirm that each speaker is present and help them do the mandatory A/V check.

During the session

• Introduce the session by welcoming the audience and reminding them of the topic of the session.
• One of your main jobs is to keep things on time. PLDI will often be dual-tracked, so it’s important to keep the two tracks roughly synchronized. Some participants decide to attend some of the talks in each session.
• We recommend following this schedule for each 20-minute slot:
  • 1-15 minutes: speaker presents their paper
  • 16-19 minute: session chair moderates Q&A
  • 19-20 minute: next speaker sets up
• Student volunteers will keep track of time, and display it on cards for you and the speaker. However, it’s your job to enforce time limits.
• Tips for keeping things on time:
  • Try to catch the speaker’s eye with about 2 minutes remaining. You can point to the time cards being displayed by the student speaker so they are aware that their slot is almost done.
  • If the speaker is still talking after 15 minutes have elapsed, stand up and politely ask them to wrap up.
  • If they are still talking after 16 minutes have elapsed, speak into the microphone and say “we’ll have to end here to stay on time; let’s thank our speaker” and start applauding.
• Tips for moderating Q&A:
  • As soon as the speaker has finished, stand up and say “Let’s thank our speaker” and start applauding. Invite the audience to ask questions.
  • Make sure people who ask questions use the mic and state their name and affiliation. Use of the microphone is essential. Please interject and insist that they use it.
  • If the audience has no questions, ask the one you prepared in advance. Usually this will be enough to get things going.
  • Check the Discord channel for your session. If any remote participants have questions, you can relay them to the room.
  • If the person asking the question goes on for a very long time, interject and ask them to bring it to a point.
  • If any questioners are belligerent or insulting, cut them off immediately and report them to the program chair (Nate Foster) or the general chair (Steve Blackburn). We sincerely hope and expect that this will not happen, but you should take action to enforce an inclusive and respectful conference environment. You can read over SIGPLAN’s non-harassment policy here, which is based on ACM’s.
• At the end of the session, thank the audience for coming, and tell them what’s happening next (coffee break, plenary, lunch, etc.)