Will the actual conference will be online this year?  Do you know
approximately when?

On Sun, May 17, 2020 at 2:15 PM Jason Hemann <jason.hem...@gmail.com> wrote:

> Hello,
>
> Thank you for your attention, and my apologies for any duplication you
> receive. Please find below the Call for Papers for the *2020 Scheme and
> Functional Programming Workshop*. The deadline has been extended to *May
> 31*. Please also note that the workshop is now to be held *virtual*ly;
> hopefully the silver lining is more and wider participation. We look
> forward to your submissions.
>
>
> *Call for Papers*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
>
>
> *Important dates*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”.
> Submission Information
> 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:
>
> http://www.sigplan.org/Resources/Author/
>
> <https://jason-hemann-dot-yamm-track.appspot.com/Redirect?ukey=1hySDOusaj9Sw1-Dfr_V_rW6365QnkXJwLSigmgTSWPE-0&key=YAMMID-39290617&link=http%3A%2F%2Fwww.sigplan.org%2FResources%2FAuthor%2F>
> 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
> <https://jason-hemann-dot-yamm-track.appspot.com/Redirect?ukey=1hySDOusaj9Sw1-Dfr_V_rW6365QnkXJwLSigmgTSWPE-0&key=YAMMID-39290617&link=http%3A%2F%2Farxiv.org%2F>
> .
>
> 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.
>
> Sincerely,
>
>
> Jason Hemann, Northeastern University
>
>
>
>
>
> *Organizing Committee*Michael D. Adams (Program Co-Chair), University of
> Michigan
> Baptiste Saleil (Program Co-Chair), IBM Canada
> Jason Hemann (Publicity Chair), Northeastern University
>
>
>
> *Program Committee*Michael D. Adams (Program Co-Chair), University of
> Michigan
> Baptiste Saleil (Program Co-Chair), IBM Canada
> Maxime Chevalier-Boisvert, Université de Montréal
> Ryan Culpepper, Czech Technical University
> Kimball Germane, University of Utah
> Yukiyoshi Kameyama, University of Tsukuba
> Andy Keep, Cisco Systems, Inc
> Julien Pagès, Université de Montréal
> Alexey Radul
>
>
>
> *Steering Committee*Will Byrd, University of Alabama at Birmingham
> Will Clinger, The Larceny Project
> Marc Feeley, Université de Montréal
> Dan Friedman, Indiana University
> Olin Shivers, Northeastern University
> [image: beacon]
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/clojure/CALcHBdFZcMrodqh-tV8BiCzOHhoVXaoKHMT4JW_2jmqcdi%3DwOQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/clojure/CALcHBdFZcMrodqh-tV8BiCzOHhoVXaoKHMT4JW_2jmqcdi%3DwOQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/CAB6_SobBR3Lq9FfZKdgO8Bgvzxi%2B1-baBncLW1S3CztsqdZLMw%40mail.gmail.com.

Reply via email to