[Haskell] CFP: Haskell Symposium 2023

2023-03-24 Thread Trevor McDonell
===
 ACM SIGPLAN CALL FOR
SUBMISSIONS

 Haskell Symposium 2023

Seattle, WA, USA
 Fri 8 -- Sat 9 September, 2023

 http://www.haskell.org/haskell-symposium/2023/



The ACM SIGPLAN Haskell Symposium 2023 will be co-located with the 2023
International Conference on Functional Programming (ICFP).

As with last year, Haskell'23 will use a single-track submission process.
That
is, we will only have the regular track and no early track.

The Haskell Symposium presents original research on Haskell, discusses
practical
experience and future development of the language, and promotes other forms
of
declarative programming.

Topics of interest include:

  * Language design, with a focus on possible extensions and modifications
of
Haskell as well as critical discussions of the status quo;

  * Theory, such as formal semantics of the present language or future
extensions, type systems, effects, metatheory, and foundations for
program
analysis and transformation;

  * Implementations, including program analysis and transformation, static
and
dynamic compilation for sequential, parallel, and distributed
architectures,
memory management, as well as foreign function and component interfaces;

  * Libraries, that demonstrate new ideas or techniques for functional
programming in Haskell;

  * Tools, such as profilers, tracers, debuggers, preprocessors, and testing
tools;

  * Applications, to scientific and symbolic computing, databases,
multimedia,
telecommunication, the web, and so forth;

  * Functional Pearls, being elegant and instructive programming examples;

  * Experience Reports, to document general practice and experience in
education, industry, or other contexts;

  * Tutorials, to document how to use a particular language feature,
programming
technique, tool or library within the Haskell ecosystem;

  * System Demonstrations, based on running software rather than novel
research
results.

Regular papers should explain their research contributions in both general
and
technical terms, identifying what has been accomplished, explaining why it
is
significant, and relating it to previous work, and to other languages where
appropriate.

Experience reports and functional pearls need not necessarily report
original
academic research results. For example, they may instead report reusable
programming idioms, elegant ways to approach a problem, or practical
experience
that will be useful to other users, implementers, or researchers. The key
criterion for such a paper is that it makes a contribution from which other
Haskellers can benefit. It is not enough simply to describe a standard
solution
to a standard programming problem, or report on experience where you used
Haskell in the standard way and achieved the result you were expecting.

Like an experience report and a functional pearl, tutorials should make a
contribution from which other Haskellers can benefit. What distinguishes a
tutorial is that its focus is on explaining an aspect of the Haskell
language
and/or ecosystem in a way that is generally useful to a Haskell audience.
Tutorials for many such topics can be found online; the distinction here is
that
by writing it up for formal review it will be vetted by experts and formally
published.

System demonstrations should summarize the system capabilities that would be
demonstrated. The proposals will be judged on whether the ensuing session is
likely to be important and interesting to the Haskell community at large,
whether on grounds academic or industrial, theoretical or practical,
technical,
social or artistic. Please contact the program chair with any questions
about
the relevance of a proposal.

If your contribution is not a research paper, please mark the title of your
experience report, functional pearl, tutorial or system demonstration as
such,
by supplying a subtitle (Experience Report, Functional Pearl, Tutorial
Paper,
System Demonstration).

Submission Details
==

Formatting
--

Submitted papers should be in portable document format (PDF), formatted
using
the ACM SIGPLAN style guidelines. Authors should use the `acmart` format,
with
the `sigplan` sub-format for ACM proceedings. For details, see:

  http://www.sigplan.org/Resources/Author/#acmart-format

It is recommended to use the `review` option when submitting a paper; this
option enables line numbers for easy reference in reviews.

Functional pearls, experience reports, tutorials and demo proposals should
be
labelled clearly as such.

Lightweight Double-blind Reviewing
--

Haskell Symposium 2023 will use a lightweight double-blind reviewing
process. To

CFP: Haskell Symposium 2023

2023-03-24 Thread Trevor McDonell
===
 ACM SIGPLAN CALL FOR
SUBMISSIONS

 Haskell Symposium 2023

Seattle, WA, USA
 Fri 8 -- Sat 9 September, 2023

 http://www.haskell.org/haskell-symposium/2023/



The ACM SIGPLAN Haskell Symposium 2023 will be co-located with the 2023
International Conference on Functional Programming (ICFP).

As with last year, Haskell'23 will use a single-track submission process.
That
is, we will only have the regular track and no early track.

The Haskell Symposium presents original research on Haskell, discusses
practical
experience and future development of the language, and promotes other forms
of
declarative programming.

Topics of interest include:

  * Language design, with a focus on possible extensions and modifications
of
Haskell as well as critical discussions of the status quo;

  * Theory, such as formal semantics of the present language or future
extensions, type systems, effects, metatheory, and foundations for
program
analysis and transformation;

  * Implementations, including program analysis and transformation, static
and
dynamic compilation for sequential, parallel, and distributed
architectures,
memory management, as well as foreign function and component interfaces;

  * Libraries, that demonstrate new ideas or techniques for functional
programming in Haskell;

  * Tools, such as profilers, tracers, debuggers, preprocessors, and testing
tools;

  * Applications, to scientific and symbolic computing, databases,
multimedia,
telecommunication, the web, and so forth;

  * Functional Pearls, being elegant and instructive programming examples;

  * Experience Reports, to document general practice and experience in
education, industry, or other contexts;

  * Tutorials, to document how to use a particular language feature,
programming
technique, tool or library within the Haskell ecosystem;

  * System Demonstrations, based on running software rather than novel
research
results.

Regular papers should explain their research contributions in both general
and
technical terms, identifying what has been accomplished, explaining why it
is
significant, and relating it to previous work, and to other languages where
appropriate.

Experience reports and functional pearls need not necessarily report
original
academic research results. For example, they may instead report reusable
programming idioms, elegant ways to approach a problem, or practical
experience
that will be useful to other users, implementers, or researchers. The key
criterion for such a paper is that it makes a contribution from which other
Haskellers can benefit. It is not enough simply to describe a standard
solution
to a standard programming problem, or report on experience where you used
Haskell in the standard way and achieved the result you were expecting.

Like an experience report and a functional pearl, tutorials should make a
contribution from which other Haskellers can benefit. What distinguishes a
tutorial is that its focus is on explaining an aspect of the Haskell
language
and/or ecosystem in a way that is generally useful to a Haskell audience.
Tutorials for many such topics can be found online; the distinction here is
that
by writing it up for formal review it will be vetted by experts and formally
published.

System demonstrations should summarize the system capabilities that would be
demonstrated. The proposals will be judged on whether the ensuing session is
likely to be important and interesting to the Haskell community at large,
whether on grounds academic or industrial, theoretical or practical,
technical,
social or artistic. Please contact the program chair with any questions
about
the relevance of a proposal.

If your contribution is not a research paper, please mark the title of your
experience report, functional pearl, tutorial or system demonstration as
such,
by supplying a subtitle (Experience Report, Functional Pearl, Tutorial
Paper,
System Demonstration).

Submission Details
==

Formatting
--

Submitted papers should be in portable document format (PDF), formatted
using
the ACM SIGPLAN style guidelines. Authors should use the `acmart` format,
with
the `sigplan` sub-format for ACM proceedings. For details, see:

  http://www.sigplan.org/Resources/Author/#acmart-format

It is recommended to use the `review` option when submitting a paper; this
option enables line numbers for easy reference in reviews.

Functional pearls, experience reports, tutorials and demo proposals should
be
labelled clearly as such.

Lightweight Double-blind Reviewing
--

Haskell Symposium 2023 will use a lightweight double-blind reviewing
process. To