caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jurriaan Hage <publicityifl@gmail.com>
To: Caml-List <caml-list@inria.fr>
Subject: [Caml-list] First call for draft papers for IFL 2020 (Implementation and Application of Functional Languages)
Date: Mon, 8 Jun 2020 05:14:04 -0700	[thread overview]
Message-ID: <CAKVFE6W8pAj27tX9OgBsbdKi8fudRmMdx51d6zMxwfnU6WuH5A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4610 bytes --]

Hello,

Please, find below the final call for draft papers for IFL 2020.
Please forward these to anyone you think may be interested.
Apologies for any duplicates you may receive.

best regards,
Jurriaan Hage
Publicity Chair of IFL

================================================================================

                                                   IFL 2020

    32nd Symposium on Implementation and Application of Functional Languages


                                               venue: online
                                   2nd - 4th September 2020

                         https://www.cs.kent.ac.uk/events/2020/ifl20/

================================================================================

### Scope

The goal of the IFL symposia is to bring together researchers actively
engaged
in the implementation and application of functional and function-based
programming languages. IFL 2020 will be a venue for researchers to present
and
discuss new ideas and concepts, work in progress, and publication-ripe
results
related to the implementation and application of functional languages and
function-based programming.

Topics of interest to IFL include, but are not limited to:

- language concepts
- type systems, type checking, type inferencing
- compilation techniques
- staged compilation
- run-time function specialisation
- run-time code generation
- partial evaluation
- (abstract) interpretation
- meta-programming
- generic programming
- automatic program generation
- array processing
- concurrent/parallel programming
- concurrent/parallel program execution
- embedded systems
- web applications
- (embedded) domain specific languages
- security
- novel memory management techniques
- run-time profiling performance measurements
- debugging and tracing
- virtual/abstract machine architectures
- validation, verification of functional programs
- tools and programming techniques
- (industrial) applications


### Post-symposium peer-review

Following IFL tradition, IFL 2020 will use a post-symposium review process
to
produce the formal proceedings.

Before the symposium authors submit draft papers. These draft papers will
be
screened by the program chair to make sure that they are within the scope
of
IFL. The draft papers will be made available to all participants at the
symposium. Each draft paper is presented by one of the authors at the
symposium.

After the symposium every presenter is invited to submit a full paper,
incorporating feedback from discussions at the symposium. Work submitted to
IFL
may not be simultaneously submitted to other venues; submissions must
adhere to ACM SIGPLAN's republication policy. The program committee will
evaluate these submissions according to their correctness, novelty,
originality,
relevance, significance, and clarity, and will thereby determine whether
the
paper is accepted or rejected for the formal proceedings. We plan to
publish
these proceedings in the International Conference Proceedings Series of the
ACM Digital Library, as in previous years.


### Important dates

Submission deadline of draft papers:           17 August 2020
Notification of acceptance for presentation:   19 August 2020
Registration deadline:                         31 August 2020
IFL Symposium:                                 2-4 September 2020
Submission of papers for proceedings:          7 December 2020
Notification of acceptance:                    3 February 2021
Camera-ready version:                          15 March 2021


### Submission details

All contributions must be written in English. Papers must use the ACM two
columns conference format, which can be found at:

              http://www.acm.org/publications/proceedings-template


### Peter Landin Prize

The Peter Landin Prize is awarded to the best paper presented at the
symposium every year. The honoured article is selected by the program
committee
based on the submissions received for the formal review process. The prize
carries a cash award equivalent to 150 Euros.


### Organisation

IFL 2020 Chair: Olaf Chitil, University of Kent, UK

IFL Publicity chair: Jurriaan Hage, Utrecht University, The Netherlands

### Virtual symposium

Because of the Covid-19 pandemic, this year IFL 2020 will be an online
event,
consisting of paper presentations, discussions and virtual social
gatherings.
Registered participants can take part from anywhere in the world.


### Acknowledgments

This call-for-papers is an adaptation and evolution of content from previous
instances of IFL. We are grateful to prior organisers for their work, which
is reused here.

[-- Attachment #2: Type: text/html, Size: 5389 bytes --]

                 reply	other threads:[~2020-06-08 12:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKVFE6W8pAj27tX9OgBsbdKi8fudRmMdx51d6zMxwfnU6WuH5A@mail.gmail.com \
    --to=publicityifl@gmail.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).