From: Michael Sperber <sperber@deinprogramm.de>
To: users@racket-lang.org, caml-list@inria.fr,
erlang-questions@erlang.org, haskell@haskell.org,
ghc-devs@haskell.org, types-announce@lists.seas.upenn.edu,
fun@cs.nott.ac.uk, lfcs-interest@inf.ed.ac.uk
Subject: [Caml-list] Call for Papers: Functional Programming for Productivity and Performance (FProPer)
Date: Fri, 11 Apr 2025 15:56:28 +0200 [thread overview]
Message-ID: <y9l1ptyssxf.fsf@deinprogramm.de> (raw)
======================================================================
*** FProPer 2025 -- CALL FOR PAPERS ***
Second ACM SIGPLAN Workshop on
Functional Programming for
Productivity and Performance
16th October 2025, Singapore
Co-located with ICFP 2025
https://conf.researchr.org/home/icfp-splash-2025/fproper-2025
======================================================================
The 2nd ACM SIGPLAN Workshop on Functional Programming for
Productivity and Performance (FProPer’25) aims to bring together
researchers and practitioners that strive to use or develop
declarative languages for combining programmer productivity with the
highest levels of runtime performance. The performance aspects are not
limited to sequential or parallel runtime performance but encompass
all kinds of performance aspects, such as memory footprint or energy
consumption as well. Application areas of interest include, but are
not limited to, high-performance scientific computing and numerical
programming.
FProPer is a satellite event of the 30th ACM SIGPLAN International
Conference on Functional Programming (ICFP 2025) held in the week of
the 12th of October in Singapore.
Although FProPer’25 is in its second year, the workshop builds on the
tradition of the FHPC and FHPNC workshops. The primary change is a
broadening of scope from high-performance and numerical computing to a
wider range of applications where programmer productivity and
performance are both being considered essential.
Information on previous workshops can be found here:
https://fhpnc.github.io/
Scope
-----
Areas of interest include, but are not limited to:
* relevant compiler technologies
* runtime systems (including fault tolerance mechanisms and those
supporting distributed or parallel computation)
* domain-specific languages (embedded or standalone)
* type systems
* formal methods
* software libraries for performance
* application studies / use case experiences.
Rather than requiring finished work typical for a conference, the
workshop aims to provide a forum where researchers and practitioners
may report promising new directions and work in progress. The workshop
will accept two kinds of submissions. Submissions for regular papers
of up to 12 pages will be solicited and reviewed by an international
committee. Accepted regular papers are expected to be published by ACM
as a workshop proceedings. Submissions for stand-alone abstracts of up
to 2 pages will be solicited and reviewed, but will not be published.
Submission Details
------------------
Submissions should fall into one of two categories:
* Regular research papers (up to 12 pages)
* Stand-alone abstracts (1 - 2 pages)
The bibliography will not be counted against the page limits for
either category.
Regular research papers are expected to present novel and interesting
research results, and will be included in the formal
proceedings. Stand-alone abstracts will be distributed to workshop
attendees, but will *not* be included in the formal proceedings.
The goal of the stand-alone abstracts is to generate discussion;
examples could include works-in-progress, surveys of current research
areas, reflections on past research, "position" papers (advocating for
specific research directions), or more generally any topic that the
authors believe would be valuable for the community. Stand-alone
abstracts will be evaluated primarily for relevance and interest.
We welcome submissions from PC members (with the exception of the PC
Chairs), but these submissions will be held to a higher standard.
Submission is handled through the HotCRP site. All submissions should
be in portable document format (PDF) and formatted using the ACM
SIGPLAN style guidelines. Submissions written with LaTeX are required
to use the acmart format and the two-column sigplan subformat (not to
be confused with the one-column acmlarge subformat!).
Stand-alone abstracts must be submitted with the label 'Extended
Abstract' clearly in the title.
Submission Link
---------------
https://fproper2025.hotcrp.com
Publication
-----------
The proceedings of FProPer 2025 will be published in the ACM Digital
Library.
Related links:
* Author Information and LaTeX templates:
http://www.sigplan.org/Resources/Author/
* Attendee Code of Conduct:
http://www.sigplan.org/Resources/Policies/CodeOfConduct/
reply other threads:[~2025-04-11 13:56 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=y9l1ptyssxf.fsf@deinprogramm.de \
--to=sperber@deinprogramm.de \
--cc=caml-list@inria.fr \
--cc=erlang-questions@erlang.org \
--cc=fun@cs.nott.ac.uk \
--cc=ghc-devs@haskell.org \
--cc=haskell@haskell.org \
--cc=lfcs-interest@inf.ed.ac.uk \
--cc=types-announce@lists.seas.upenn.edu \
--cc=users@racket-lang.org \
/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