caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sam Tobin-Hochstadt <>
Subject: [Caml-list] ICFP 2021 Student Research Competition: Call for Submissions
Date: Wed, 16 Jun 2021 22:40:46 -0400	[thread overview]
Message-ID: <60cab62e5369e_4e48e2940c8@homer.mail> (raw)

ICFP 2021 Student Research Competition
       Call for Submissions

ICFP invites students to participate in the Student Research
Competition, which will be held virtually alongside the main
conference, in order to present their research and receive
feedback from prominent members of the programming language
research community.

As usual, the SRC consists of three rounds:

* Extended abstract
* Poster session at ICFP 2021
* ICFP presentation

To make the virtual competition fruitful, we will make sure
that every student will have an "invited audience" during the
poster session.  We are also planning to organize a social event
for the students.  Please visit the SRC website for updates.

### Important Dates

Submissions due: 2 July 2021 (Friday)
Notification: 16 July 2021 (Friday)
Conference: 22 August (Sunday) - 27 August (Friday)

### Submission Details

Each submission (referred to as "abstract" below) should include the
student author’s name and e-mail address; institutional affiliation;
research advisor’s name; ACM student member number; category
(undergraduate or graduate); research title; and an extended abstract
addressing the following:

* Problem and Motivation: Clearly state the problem being addressed and
explain the reasons for seeking a solution to this problem.

* Background and Related Work: Describe the specialized (but
pertinent) background necessary to appreciate the work in the
context of ICFP areas of interest. Include references to the
literature where appropriate, and briefly explain where your work
departs from that done by others.

* Approach and Uniqueness: Describe your approach in addressing the
problem and clearly state how your approach is novel.

* Results and Contributions: Clearly show how the results of your work
contribute to programming language design and implementation in
particular and to computer science in general; explain the
significance of those results.

* Submissions must be original research that is not already published
at ICFP or another conference or journal. One of the goals of the
SRC is to give students feedback on ongoing, unpublished
work. Furthermore, the abstract must be authored solely by the
student. If the work is collaborative with others and*or part of a
larger group project, the abstract should make clear what the
student’s role was and should focus on that portion of the work.

* Formatting: Submissions must be in PDF format, printable in black
and white on US Letter sized paper, and interpretable by common PDF
tools. All submissions must adhere to the "ACM Small" template that
is available (in both LaTeX and Word formats) from For authors
using LaTeX, a lighter-weight package, including only the essential
files, is available from The submission
must not exceed 3 pages in PDF format. Reference lists do not count
towards the 3-page limit.

Further information is available at the ICFP SRC website:

Program Committee:
Chair: Anders Miltner (UT Austin)
Andreea Costea (NUS Singapore)
Andrew Hirsch (MPI-SWS)
Liam O'Connor (University of Edinburgh)
Lionel Parreaux (HKUST)
Daming Zou (ETH Zurich)

                 reply	other threads:[~2021-06-17  2:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60cab62e5369e_4e48e2940c8@homer.mail \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).