Blogs >>
ICFP 2017
Sun 3 - Sat 9 September 2017 Oxford, United Kingdom

The Scheme and Functional Programming Workshop is a yearly meeting of programming language practitioners who share a sense of aesthetic as embodied by the Algorithmic Language Scheme: universality through minimalism, adequation through self-improvement, flexibility through rigorous design, and composability through orthogonal features.

Sun 3 Sep

09:00 - 09:10: Scheme 2017 - Session 0 at L4
scheme-2017150442200000009:00 - 09:10
Day opening
09:10 - 10:10: Scheme 2017 - Session 1 at L4
scheme-2017150442260000009:10 - 10:10
12:00 - 12:30: Scheme 2017 - Session 3 at L4
scheme-2017150443280000012:00 - 12:30
14:00 - 15:00: Scheme 2017 - Session 4 at L4
scheme-2017150444000000014:00 - 14:45
scheme-2017150444270000014:45 - 15:00
15:30 - 16:30: Scheme 2017 - Session 5 at L4
scheme-2017150444540000015:30 - 16:15
scheme-2017150444810000016:15 - 16:30
16:50 - 17:50: Scheme 2017 - Session 6 at L4
scheme-2017150445020000016:50 - 17:20
scheme-2017150445200000017:20 - 17:50
Day closing

Call for Papers

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, ECMAcript, 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 Information

Please submit full papers and experience reports to our Submission Page.

[NEW IN 2017!] Paper submissions must use the format acmart and its sub-format acmlarge. 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 change is in line with ACM conferences (such as ICFP with which we are colocated) switching from their traditional two-column formats (e.g. sigplanconf) to the above. While a two-column format with small fonts is much more practical when reading printed papers, the single-column format with large fonts is nicer to view on a computer screen, as most papers are read these days.

To encourage authors to submit their best work, we offer three tracks:

Full Papers, with a limit to 24 pages. Each accepted paper will be presented by its authors in a 40 minute slot including Q&A. Experience Reports, with a limit to 12 pages. Each accepted report will be presented by its authors in a 20 minute slot including Q&A. Lightning talks, with a limit to 192 words. Each accepted lightning talk will be presented by its authors in a 5 minute slot including 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 Indiana University.

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.