Research PapersECOOP 2022

Accepted Papers

	Title
	Accumulation AnalysisVCOOP 2022 Research Papers Martin Kellogg, Narges Shadab, Manu Sridharan, Michael D. Ernst
	A Deterministic Memory Allocator for Dynamic Symbolic ExecutionVCOOP 2022ECOOP 2022 Research Papers Daniel Schemmel, Julian Büning, Frank Busse, Martin Nowack, Cristian Cadar
	API Generation for Multiparty Session Types, Revisited and Revised using Scala 3 (Pearl)VCOOP 2022ECOOP 2022 Research Papers Guillermina Cledou, Luc Edixhoven, Sung-Shik Jongmans, José Proença
	A Self-Dual Distillation of Session Types (Pearl)VCOOP 2022ECOOP 2022 Research Papers Jules Jacobs Pre-print
	Automatic Root Cause Quantification for Missing Edges in JavaScript Call GraphsVCOOP 2022 Research Papers Madhurima Chakraborty, Renzo Olivares, Manu Sridharan, Behnaz Hassanshahi Pre-print
	Compiling Volatile Correctly in JavaVCOOP 2022 Research Papers Shuyang Liu, John Bender, Jens Palsberg
	Concolic Execution for WebAssemblyECOOP 2022 Research Papers Filipe Marques, José Fragoso Santos, Nuno Santos, Pedro Adão
	Defining Corecursive Functions in Coq Using ApproximationsVCOOP 2022ECOOP 2022 Research Papers Vlad Rusu, David Nowak
	Design-by-Contract for Flexible Multiparty Session Protocols - Choreography Automata for distributed TypeScript programmingECOOP 2022 Research Papers Lorenzo Gheri, Ivan Lanese, Emilio Tuosto, Nobuko Yoshida, Neil Anthony Sayers
	Direct Foundations for Compositional ProgrammingVCOOP 2022 Research Papers Andong Fan, Xuejing Huang, Han Xu, Yaozhu Sun, Bruno C. d. S. Oliveira Pre-print Media Attached
	Elementary Type InferenceVCOOP 2022 Research Papers Jinxu Zhao, Bruno C. d. S. Oliveira
	Experience: Model-Based Feedback-Driven Greybox Fuzzing for Web ApplicationsVCOOP 2022 Research Papers François Gauthier, Behnaz Hassanshahi, Benjamin Selwyn-Smith, Trong Nhan Mai, Max Schlüter, Micah Williams
	Fair Termination of Multiparty SessionsECOOP 2022 Research Papers Luca Ciccone, Francesco Dagnino, Luca Padovani
	Ferrite: A Judgmental Embedding of Session Types in RustVCOOP 2022ECOOP 2022 Research Papers Ruo Fei Chen, Stephanie Balzer, Bernardo Toninho Pre-print
	Functional programming for distributed systems with XCVCOOP 2022ECOOP 2022 Research Papers Giorgio Audrito, Roberto Casadei, Ferruccio Damiani, Guido Salvaneschi, Mirko Viroli Pre-print
	Functional Programming with DatalogECOOP 2022 Research Papers André Pacak, Sebastian Erdweg
	Global Type Inference for Featherweight Generic JavaVCOOP 2022ECOOP 2022 Research Papers Andreas Stadelmeier, Martin Plümicke, Peter Thiemann
	Hinted Dictionaries: Efficient Functional Ordered Sets and MapsECOOP 2022 Research Papers Amir Shaikhha, Hesam Shahrokhi, Mahdi Ghorbani
	How to Take the Inverse of a TypeECOOP 2022 Research Papers Danielle Marshall, Dominic Orchard Pre-print
	JavaScript Sealed ClassesECOOP 2022 Research Papers Manuel Serrano
	Low-Level Bi-AbductionECOOP 2022 Research Papers Lukáš Holík, Petr Peringer, Adam Rogalewicz, Veronika Šoková, Tomáš Vojnar, Florian Zuleger
	Maniposynth: Bimodal Tangible Functional ProgrammingVCOOP 2022 Research Papers Brian Hempel, Ravi Chugh Pre-print Media Attached
	NWGraph: A Library of Generic Graph Algorithms and Data Structures in C++20VCOOP 2022 Research Papers Andrew Lumsdaine, Luke Dalessandro, Jesun Sahariar Firoz, Xu Liu, Phil Ratzloff, Scott McMillan, Marcin, Kevin Deweese
	PEDroid: Automatically Extracting Patches from Android App UpdatesVCOOP 2022 Research Papers Hehao Li, Yizhuo Wang, Yiwei Zhang, Juanru Li, Dawu Gu
	Prisma: A tierless language for enforcing contract-client protocols in decentralized appsVCOOP 2022ECOOP 2022 Research Papers David Richter, David Kretzler, Pascal Weisenburger, Guido Salvaneschi, Sebastian Faust, Mira Mezini Pre-print Media Attached
	Qilin: A New Framework for Supporting Fine-Grained Context-Sensitivity in Java Pointer AnalysisVCOOP 2022 Research Papers Dongjie He, Jingbo Lu, Jingling Xue
	REST: Integrating Term Rewriting with Program VerificationVCOOP 2022ECOOP 2022 Research Papers Zachary Grannan, Eva Darulova, Alexander J. Summers, Niki Vazou
	Slicing of Probabilistic Programs based on SpecificationsECOOP 2022 Research Papers Federico Olmedo Pre-print
	Static Analysis for AWS Best Practices in Python CodeVCOOP 2022ECOOP 2022 Research Papers Rajdeep Mukherjee, Omer Tripp, Ben Liblit, Michael Wilson DOI
	Stay Safe under Panic: Affine Rust Programming with Multiparty Session TypesVCOOP 2022ECOOP 2022 Research Papers Nicolas Lagaillardie, Rumyana Neykova, Nobuko Yoshida
	Synchron - An API and Runtime for Embedded SystemsECOOP 2022 Research Papers Abhiroop Sarkar, Bo Joel Svensson, Mary Sheeran Pre-print
	Union Types with Disjoint SwitchesVCOOP 2022ECOOP 2022 Research Papers Baber Rehman, Xuejing Huang, Ningning Xie, Bruno C. d. S. Oliveira
	Verified Compilation and Optimization of Floating-Point Programs in CakeMLVCOOP 2022ECOOP 2022 Research Papers Heiko Becker, Robert Rabe, Eva Darulova, Magnus O. Myreen, Zachary Tatlock, Ramana Kumar, Yong Kiam Tan, Anthony C. J. Fox
	Vincent: Green Hot Methods in the JVMVCOOP 2022 Research Papers Kenan Liu, Khaled Mahmoud, Joonhwan Yoo, Yu David Liu Pre-print
	What If We Don’t Pop the Stack? The Return of Second-Class ValuesVCOOP 2022 Research Papers Anxhelo Xhebraj, Oliver Bračevac, Guannan Wei, Tiark Rompf Link to publication DOI

Call for Papers

ECOOP is a conference about programming originally focused on object-orientation, but now including all practical and theoretical investigations of programming languages, systems and environments. ECOOP solicits innovative solutions to real problems as well as evaluations of existing solutions.

Authors are asked to pick one of the following categories:

• Research. The most traditional category for papers that advance the state of the art.
• Reproduction. An empirical evaluation that reconstructs a published experiment in a different context in order to validate the results of that earlier work.
• Experience. Applications of known PL techniques in practice as well as tools. Industry papers will be reviewed by practitioners. We welcome negative results that may provide inspiration for future research.
• Pearls/Brave New Ideas. Articles that either explain a known idea in an elegant way or unconventional papers introducing ideas that may take some time to substantiate. These papers may be short.

Submissions

Submission must not have been published, or have major overlap with previous work. In case of doubt, contact the chair. Proceedings are published in open access by Dagstuhl LIPIcs in the Dagstuhl LIPIcs LaTeX-style template. To reduce friction when resubmitting, ACM’s PACMPL and TOPLAS formatted papers can be submitted as such (with the understanding that if accepted, they will be reformatted).

ECOOP uses double-blind reviewing. Authors’ identities are only revealed if a paper is accepted. Papers must omit author names and institutions, and use the third person when referencing the authors’ own work. Nothing should be done in the name of anonymity that weakens the submission; see the DB FAQ. /if in doubt, contact the chairs.

There is no page limit on submissions, but authors must understand that reviewers have a fixed time budget for each paper, so the length of the feedback is likely to be unaffected by length. Brevity is a virtue.

Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no length limit.

ECOOP 2022 will have two deadlines for submissions, three months apart. Future years may have more deadlines. Papers submitted in each round can be (a) accepted, (b) rejected, or (c) asked for revisions. Revisions can be submitted at a later round. Papers retain their reviewers during revision.

Artifact Evaluation and Intent

To support replication of experiments, authors of research papers may submit artifacts to the Artifact Evaluation Committee. They will be asked whether they intend to submit an artifact at submission time. It is understood that some paper do not have artifacts. AEC members will serve on the extended review committee.

Journal First and Journal After

We have Journal First / After arrangements with ACM’s Transactions on Programming Languages and Systems (TOPLAS), Elsevier’s Science of Computer Programming (SCP) and AITO’s Journal of Object Technology (JOT).

Only new research papers are eligible to be Journal First (JF). JF papers will have an extended abstract in the ECOOP proceedings. The deadline is that same as round 1 of submissions and the notification is aligned with round 2 notification. TOPLAS JF papers should be submitted according to this announcement. SCP JF papers should follow this call for papers. JF papers are presented at the conference and eligible for awards.

Journal After (JA) papers are papers for which the authors request to be considered for post conference journal publication. Once accepted by the ECOOP PC, these papers will be forwarded to the journal editors. Reviews and reviewers will be forwarded and used at the editor’s discretion. JA papers will have an extended abstract (up to 12 pages) in the conference proceedings.

Frequently Asked Questions

Multiple deadlines

Q: What are use-cases of the new submission process?

Overall, multiple deadlines are meant to speed up the reviewing cycle and better support revisions. Our expectation is that more papers will be accepted with this new process.

• A paper is submitted in R1. Reviewers find it good as is, the paper is accepted. A preprint is added to the conference website as soon as the camera ready copy is complete. The paper is presented at ECOOP’22.

• A paper is submitted in R1. The reviewers requires changes. Authors have one month to revise and resubmit for R2. The same reviewers check the paper, and accept it. Authors have one more month to finalise their work. The paper is presented at ECOOP’22.

• A paper is submitted in R2. The reviewers require changes. The paper will not be presented at ECOOP’22. Authors can resubmit at the next deadline (TBA). The same reviewers check the paper, if accepted, a pre-print is put on the ECOOP’23 website and the paper is presented in 2023.

Artifacts

Q: Are artifacts required?

No! But if an artifact is not provided, the authors must explain why their work is not available for repetition.

Q: Can a paper be accepted if the artifact is rejected?

Yes! The reasons for rejecting an artifact are multiple and often stem from the quality of the packaging.

Q: Can an artifact help clear up confusion about a paper’s result?

Yes! That is the whole point of allowing artifacts to be submitted together with the paper.

Q: Who reviews artifacts?

The Artifact Evaluation Committee as usual.

Authors: Double-Blinding Submissions

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

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.

Q: Should I change the name of my system?

No.

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

Cite the code in your paper, but remove the URL and, instead say “link to repository removed for double blind review”. If you believe reviewer access to your code would help during author response, contact the chair.

Q: I am submitting an extension of my workshop paper, should I anonymize reference to that work?

No. But we recommend to change the title to distinguish the papers.

Q: Am I allowed to post my paper on my web page or arXiv? send it to colleagues? give a talk about it? on social media?

There is a tension between the normal communication of scientific results and actions that essentially force potential reviewers to learn the identity of authors. Roughly speaking, you may 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. Things you may do:

• Put your submission on your home page.
• Discuss your work with anyone not on the review committees.
• Present your work at professional meetings, workshops, job interviews, etc.
• Post on arXiv or a similar site.

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 us.

Reviewers: Double-blind

Q: What should I do if I if I learn the authors’ identity?

If at any point you feel that the authors’ actions are largely aimed at ensuring that potential reviewers know their identity, you should contact the Program Chair. Otherwise you should not treat double-blind reviewing differently from regular blind reviewing. In particular, you should 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: The authors provided a URL to supplemental material, what should I do?

Contact the Chair, who will download the material on your behalf.

Q: Can I seek an outside review?

No.

(based on the PLDI’20 DBR FAQ.)

We would like to thank and congratulate our ECOOP’22 Distinguished Reviewers for their exceptional contributions:

• Jeremy Gibbons, University of Oxford
• Simon Fowler, University of Glasgow
• Juliana Franco, DeepMind
• Vlastimil Dort, Charles University