The Scheme and Functional Programming Workshop is a yearly meeting of programming language practitioners who share an aesthetic sense embodied by the Algorithmic Language Scheme: universality through minimalism, and flexibility through rigorous design.
NOTE: Deadline changed to 31 May
NOTE: Author notification date changed to 19 June
NOTE: Camera Ready date changed to 7 July
NOTE: acmart format clarified to be sigplan
Fri 28 Aug Times are displayed in time zone: Eastern Time (US & Canada) change
|10:00 - 11:00|
|SICP JS: Ketchup on Caviar?|
|11:30 - 12:00|
|Clotho: A Racket Library for Parametric Randomness|
|12:00 - 12:30|
|Scheme for scientific computing|
Francesco MontanariUniversidad Autónoma de MadridFile Attached
|12:30 - 12:40|
|Designing a Programming Environment Based on the Program Design Recipe (Lightning Talk)|
Junya NoseTokyo Institute of Technology, Youyou CongTokyo Institute of Technology, Hidehiko MasuharaTokyo Institute of TechnologyFile Attached
|12:40 - 12:50|
|On Teaching Type Systems as Macros (Lightning Talk)|
Youyou CongTokyo Institute of Technology, Naoya FurudonoTokyo Institute of Technology, Hidehiko MasuharaTokyo Institute of TechnologyFile Attached
|12:50 - 13:00|
|Programming with Petri Nets to Reason about Concurrency (Lightning Talk)|
julien lepillerYale UniversityFile Attached
|14:30 - 15:00|
|Running Scheme On Bare Metal (Experience Report)|
|15:00 - 15:30|
|Experience Report on Solving the Problem Set of SICP completely.|
Vladimir NikishkinUnaffiliatedFile Attached
|16:00 - 17:00|
|21st Century Lisp in Academic Research and Pedagogy|
Call for Papers
NOTE: Deadline changed to 31 May
The 2020 Scheme and Functional Programming Workshop is calling for submissions.
We invite high-quality papers about novel research results, lessons learned from practical experience in industrial or educational setting, and even new insights on old ideas. We welcome and encourage submissions that apply to any language that can be considered Scheme: from strict subsets of RnRS to other “Scheme” implementations, to Racket, to Lisp dialects including Clojure, Emacs Lisp, Common Lisp, to functional languages with continuations and/or macros (or extended to have them) such as Dylan, ECMAScript, Hop, Lua, Scala, Rust, etc. The elegance of the paper and the relevance of its topic to the interests of Schemers will matter more than the surface syntax of the examples used. Topics of interest include (but are not limited to):
- Interaction: program-development environments, debugging, testing, refactoring
- Implementation: interpreters, compilers, tools, garbage collectors, benchmarks
- Extension: macros, hygiene, domain-specific languages, reflection, and how such extension affects interaction.
- Expression: control, modularity, ad hoc and parametric polymorphism, types, aspects, ownership models, concurrency, distribution, parallelism, non-determinism, probabilism, and other programming paradigms
- Integration: build tools, deployment, interoperation with other languages and systems
- Formal semantics: Theory, analyses and transformations, partial evaluation
- Human Factors: Past, present and future history, evolution and sociology of the language Scheme, its standard and its dialects
- Education: approaches, experiences, curricula
- Applications: industrial uses of Scheme
- Scheme pearls: elegant, instructive uses of Scheme
- Submission deadline is 31 May 2020.
- Authors will be notified by 12 June 2020.
- Camera-ready versions are due 30 June 2020.
- All deadlines are (23:59 UTC-12), “Anywhere on Earth”.
Paper submissions must use the format acmart and its sub-format sigplan. They must be in PDF, printable in black and white on US Letter size. Microsoft Word and LaTeX templates for this format are available at:
This format is in line with ACM conferences (such as ICFP with which we are colocated). It is recommended to use the review option when submitting a paper; this option enables line numbers for easy reference in reviews.
We want to encourage all kinds of submissions, including full papers, experience reports and lightning talks. Papers and experience reports are limited to 14 pages, but we encourage submitting smaller papers. Lightning talks are limited to 192 words. Each accepted paper and report will be presented by its authors in a 25 minute slot including Q&A. Each accepted lightning talk will be presented by its authors in a 5 minute slot, followed by 5 minutes of Q&A.
The size limits above exclude references and any optional appendices. There are no size limits on appendices, but the papers should stand without the need to read them, and reviewers are not required to read them.
Authors are encouraged to publish any code associated to their papers under an open source license, so that reviewers may try the code and verify the claims.
Proceedings will be printed as a Technical Report at the University of Michigan and uploaded to arXiv.org.
Publication of a paper at this workshop is not intended to replace conference or journal publication, and does not preclude re-publication of a more complete or finished version of the paper at some later conference or in a journal.
Scheme 2020 use lightweight-double-blind reviewing. Submitted papers must omit author names and institutions and reference the authors’ own related work in the third person (e.g., not “we build on our previous work…” but rather “we build on the work of…”).
The purpose is to help the reviewers come to an initial judgement about the paper without bias, not to make it impossible for them to discover the authors if they were to try. Nothing should be done in the name of anonymity that weakens the submission or makes the job of reviewing the paper more difficult (e.g., important background references should not be omitted or anonymized).
- Full papers and experience reports should use the
- Lightning talks can be submitted as either a text file or a PDF file.
- It is recommended to use the
acmartwhen submitting a paper; these options hide the author names and enable line numbers for easy reference in review.
Submissions will be accepted via the Scheme 2020 HotCRP instance: