[ The Types Forum (announcements only),
http://lists.seas.upenn.edu/mailman/listinfo/types-announce ]
TL;DR: The GPCE paper submission deadline is earlier this year but was just
extended to 12 March 2026. Also, there is no abstract submission deadline –
submit your papers directly at
https://urldefense.com/v3/__https://gpce26.hotcrp.com/__;!!IBzWLUs!TqEMiWcqwU4uBv6hE4lDbaj5yzIy6S9zkx_ws8KDpO6My3KF8V076LCaSdj8-guWb9NCIGWGHVJ5TxUAUTgWqhJf7TySN-s$
.
Like last year, GPCE will be co-located with ECOOP rather than SPLASH. The
ECOOP conference will be hosted in Brussels, Belgium, between Mon 29 June and
Fri 3 July 2026.
We are interested in all topics related to generative programming, including
(but not limited to) topics from type theory to software engineering and AI
code generation.
GPCE 2026 website:
https://urldefense.com/v3/__https://2026.ecoop.org/home/gpce-2026__;!!IBzWLUs!TqEMiWcqwU4uBv6hE4lDbaj5yzIy6S9zkx_ws8KDpO6My3KF8V076LCaSdj8-guWb9NCIGWGHVJ5TxUAUTgWqhJfAf2iSRg$
---------------------------
Call for Papers
---------------------------
The ACM SIGPLAN International Conference on Generative Programming: Concepts &
Experiences (GPCE) is a conference at the intersection of programming languages
and software engineering, focusing on techniques and tools for code generation,
language implementation, model-driven engineering, and product-line development.
---------------------------
Topics of Interest:
---------------------------
GPCE seeks conceptual, theoretical, empirical, and technical contributions to
its topics of interest, which include but are not limited to:
- program transformation, staging,
- macro systems, preprocessors,
- program synthesis,
- code-recommendation systems,
- domain-specific languages,
- generative language workbenches,
- language embedding, language design,
- domain engineering,
- software product lines, configurable software,
- feature interactions,
- applications and properties of code generation,
- language implementation,
- AI/ML techniques for generative programming,
- generative programming for AI/ML techniques,
- model-driven engineering, low code / no code approaches.
GPCE promotes cross-fertilization between programming languages and software
development and among different styles of generative programming in its
broadest sense.
Authors are welcome to check with the PC chair whether their planned papers are
in scope.
---------------------------
Paper Categories
---------------------------
GPCE solicits four kinds of submissions:
- Full Papers: reporting original and unpublished results of research that
contribute to scientific knowledge for any GPCE topic. Full paper submissions
must not exceed 10 pages excluding the bibliography.
- Short Papers: presenting unconventional ideas or new visions in any GPCE
topics. Short papers do not always contain complete results as in the case of
full papers, but can introduce new ideas to the community and get early
feedback. Note that short papers are not intended to be position statements.
Accepted short papers are included in the proceedings and will be presented at
the conference. Short paper submissions must not exceed 5 pages excluding the
bibliography, and must have the text “(Short Paper)” appended to their titles.
- Tool Demonstrations: presenting tools for any GPCE topic. Tools must be
available for use and must not be purely commercial. Submissions must provide a
tool description not exceeding 5 pages excluding bibliography and a separate
demonstration outline including screenshots also not exceeding 5 pages. Tool
demonstration submissions must have the text “(Tool Demonstration)” appended to
their titles. If they are accepted, tool descriptions will be included in the
proceedings. The demonstration outline will only be used to evaluate the
planned demonstration.
- Generative Pearl: is an elegant essay about generative programming. Examples
include but are not limited to an interesting application of generative
programming and an elegant presentation of a (new or old) data structure using
generative programming (similar to Functional Pearl in ICFP and Pearl in
ECOOP). Accepted Generative Pearl papers are included in the proceedings and
will be presented at the conference. Generative Pearl submissions must not
exceed 10 pages excluding the bibliography, and must have the text “(Generative
Pearl)” appended to their titles.
---------------------------
Paper Selection
---------------------------
The GPCE program committee will evaluate each submission according to the
following selection criteria:
- Novelty. Papers must present new ideas or evidence and place them
appropriately within the context established by previous research in the field.
- Significance. The results in the paper must have the potential to add to the
state of the art or practice in significant ways.
- Evidence. The paper must present evidence supporting its claims. Examples of
evidence include formalizations and proofs, implemented systems, experimental
results, statistical analyses, and case studies.
- Clarity. The paper must present its contributions and results clearly.
---------------------------
Best Paper Award
---------------------------
Following the tradition, the GPCE program committee will select the best paper
among accepted papers. The authors of the best paper will be given the best
paper award at the conference.
---------------------------
Paper Submission
---------------------------
Papers must be submitted using HotCRP:
https://urldefense.com/v3/__https://gpce26.hotcrp.com/__;!!IBzWLUs!TqEMiWcqwU4uBv6hE4lDbaj5yzIy6S9zkx_ws8KDpO6My3KF8V076LCaSdj8-guWb9NCIGWGHVJ5TxUAUTgWqhJf7TySN-s$
.
All submissions must use the ACM SIGPLAN Conference Format “acmart”. Be sure to
use the latest LaTeX templates and class files, the SIGPLAN sub-format, and
10-point font. Consult the `sample-sigplan.tex` template and use the
document-class `\documentclass[sigplan,anonymous,review]{acmart}`.
To increase fairness in reviewing, GPCE uses the **double-blind review
process** which has become standard across SIGPLAN conferences:
- Author names, institutions, and acknowledgments should be omitted from
submitted papers, and
- references to the authors’ own work should be in the third person.
No other changes are necessary, and authors will not be penalized if reviewers
are able to infer authors’ identities in implicit ways.
By submitting your article to an ACM Publication, you are hereby acknowledging
that you and your co-authors are subject to all ACM Publications Policies,
including ACM’s new Publications Policy on Research Involving Human
Participants and Subjects. Alleged violations of this policy or any ACM
Publications Policy will be investigated by ACM and may result in a full
retraction of your paper, in addition to other potential penalties, as per ACM
Publications Policy.
Please ensure that you and your co-authors obtain an ORCID ID, so you can
complete the publishing process for your accepted paper. ACM has been involved
in ORCID from the start and we have recently made a commitment to collect ORCID
IDs from all of our published authors. The collection process has started and
will roll out as a requirement throughout 2022. We are committed to improve
author discoverability, ensure proper attribution and contribute to ongoing
community efforts around name normalization; your ORCID ID will help in these
efforts.
AUTHORS TAKE NOTE: The official publication date is the date the proceedings
are made available in the ACM Digital Library. This date may be up to two weeks
prior to the first day of your conference. The official publication date
affects the deadline for any patent filings related to published work.
For additional information, clarification, or answers to questions, contact the
program chair.
---------------------------
ACM Artifact Badges
---------------------------
There as been quite some momentum in recent years to improve replication and
reproducibility in software engineering. Starting the 2024 edition, we want to
give authors the chance to apply for an ACM Artifact Badge. Even though the
artifact submission is not mandatory, we recommend authors to submit their
artifacts to reach a higher impact with their research.
Authors that want to apply for an ACM Artifact Badge are asked to add a brief
paragraph in the Acknowledgments section of their submission. The paragraph
should indicate which ACM Badge is the submission aiming for (see ACM page
linked below) and what is part of the artifact. The paragraph may be removed
for the final version of the paper, if it is clear from the manuscript what
constitutes the artifact.
Only the artifacts of accepted papers will be reviewed (the artifacts of
rejected submissions will not be reviewed at all). The received artifact badges
will be announced shortly before the camera ready version is due.
More information on ACM Artifact Badges:
https://urldefense.com/v3/__https://www.acm.org/publications/policies/artifact-review-and-badging-current__;!!IBzWLUs!TqEMiWcqwU4uBv6hE4lDbaj5yzIy6S9zkx_ws8KDpO6My3KF8V076LCaSdj8-guWb9NCIGWGHVJ5TxUAUTgWqhJfiJ2x9Go$
---------------------------
Important Dates
---------------------------
Paper submission: Thu 12 Mar 2026
Author response period: Mon 13 - Thu 16 Apr 2026
Author Notification: Thu 23 Apr 2026
Conference: Mon 29 Jun 2026
---------------------------
Questions? Use the GPCE contact form:
https://urldefense.com/v3/__https://2026.ecoop.org/contact2/ecoop-gpce-2026__;!!IBzWLUs!TqEMiWcqwU4uBv6hE4lDbaj5yzIy6S9zkx_ws8KDpO6My3KF8V076LCaSdj8-guWb9NCIGWGHVJ5TxUAUTgWqhJfxNk9ye8$
