2024-06-22

[Caml-list] UNIF 2024 - Call for Participation

[Apologies for multiple copies]

     UNIF 2024: CALL FOR PARTICIPATION
The 38th International Workshop on Unification
             Nancy, France, July 2, 2024
A satellite workshop of CADE/IJCAR, affiliated with IJCAR

Website: https://lat.inf.tu-dresden.de/unif2024


* The International Workshop on Unification (UNIF) is a yearly forum
  devoted to unification theory and its applications. Unification is
  concerned with the problem of making two given terms equal, either
  syntactically or modulo an equational theory. It is a fundamental
  process used in various areas of computer science, including automated
  reasoning, term rewriting, logic programming, natural language
  processing, program analysis, knowledge representation, types, etc.

* A non-exhaustive list of topics of interest includes: syntactic and
  equational unification algorithms; matching and constraint solving;
  higher-order unification; unification in modal, temporal, and
  description logics; admissibility of inference rules; narrowing;
  disunification; anti-unification; complexity issues; combination
  methods; implementation techniques; applications.

* Invited speakers: George Metcalfe (University of Bern), Daniele
  Nantes-Sobrinho (Universidade de Brasília, Imperial College London)

* The details of the invited talks, list of accepted contributions and
  the schedule of technical program are available on the webpage.

* Registration: visit the IJCAR registration webpage at:
  https://merz.gitlabpages.inria.fr/2024-ijcar/page/registration/
  (registration possible until June 24)
Posted by at No comments:

2024-06-17

[Caml-list] PLMW@ICFP'24: Final call for Participation (travel funding application by June 21)

APPLICATION FOR PLMW TRAVEL FUNDING

For full consideration for scholarship funding, please apply at the link below by June 21, AoE. We will notify accepted attendees in a rolling fashion until all funding is committed.

The application can be accessed at the following URL  (Apply by June 21, 2024 AOE for full consideration!):
https://forms.gle/vC6udnMWRvvAczPR6

—--------------------------------------------------------------

ACM SIGPLAN Programming Languages Mentoring Workshop (PLMW) at ICFP 24, Milan, Italy

Workshop: Monday, September 2, 2024
Website: https://icfp24.sigplan.org/home/PLMW-ICFP-2024

PLMW is a workshop co-located with ICFP 2024 (the International Conference on Functional Programming) in Milan, Italy, from September 2-7.

The purpose of this mentoring workshop is to encourage graduate students and senior undergraduate students to pursue careers in programming language research. This workshop will bring together world leaders in programming languages research and teaching from academia and industry to help students imagine how they might contribute to our research community. Topics will range from the abstract (e.g., what is PL research and how does one become involved in it) to the concrete (e.g., how to navigate an academic conference, how to pick a research area) as well as technical talks on cutting-edge topics.

We especially encourage women and underrepresented minority students, and people with disabilities to attend PLMW.

This workshop is part of the activities surrounding ICFP, and takes place the day before the main conference. One goal of the workshop is to make the ICFP conference more accessible to newcomers. We hope that participants will stay through the entire conference.

Note that ICFP and PLMW are planned to be largely in-person events. While we recognize that travel to conferences is not easy for everyone, we do hope you will be able to join us in person to get the most out of the conference and its community-building aspects.

A number of sponsors have generously donated scholarship funds for qualified students to attend PLMW. These scholarships can cover expenses (airfare, hotel, and registration fees) for attendance at both the workshop and the ICFP conference.

Students attending this year will get one year free student membership of SIGPLAN, unless they prefer to opt out during their application.

The workshop registration is open to all. Students with alternative sources of funding are welcome as well.


Posted by at No comments:

2024-06-13

[Caml-list] POPL 2025: Call for Workshops and Co-located Events

CALL FOR WORKSHOPS AND CO-LOCATED EVENTS

                    POPL 2025

      52nd ACM SIGPLAN-SIGACT  Symposium on
      Principles of Programming Languages

         Sun 19 - Sat 25, January 2025
           Denver, Colorado, United States

          https://popl25.sigplan.org

The 52nd ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages (POPL 2025) will be held in Denver, Colorado, United States.

POPL provides a forum for the discussion of fundamental principles and important innovations in the design, definition, analysis, transformation, implementation and verification of programming languages, programming systems, and programming abstractions.

Events focusing on experimental and theoretical topics are welcome.

Proposals are invited for workshops and other events to be co-located with POPL 2025. All co-located events are sponsored by SIGPLAN (http://acm.org/sigplan/).

Workshops should be more informal and focused than POPL itself, and include sessions that enable interaction among the workshop attendees. The preference is for one-day workshops, but other schedules can also be considered.

---------------------------------------------------------------------

Submission details

Deadline for submission: 26 July 2024

Notification of acceptance: 2 August 2024

A workshop proposal should provide the following information:

* Name of the workshop.
* Duration of the workshop.
* Whether the workshop will be Conference-approved or SIGPLAN-approved (see below).
* Organizers: names, affiliation, contact information, brief (100 words) biography.
* A short description (150-200 words) of the topic.
* Event format: workshop; type of submissions if any; review process; results dissemination.
* Expected attendance and target audience.
* Potential PC members - please do not contact them before the workshop is approved.
* History of the workshop.
* Plans for remote participation

Proposals must be submitted in PDF form by email with the subject POPL 2025 Workshop Proposal: [workshop name], to the workshop co-chairs: Christoph Matheja (chmat@dtu.dk) and Robert Rand (rand@uchicago.edu).

---------------------------------------------------------------------

SIGPLAN Sponsorship

POPL co-located events are sponsored by SIGPLAN (http://sigplan.org/). There are two kinds of co-located events: Conference-approved (no proceedings) and SIGPLAN-approved (proceedings in the ACM Digital Library). See http://www.sigplan.org/Resources/Guidelines/Workshops/ for more information, including a full listing of prescriptions for Conference-approved and SIGPLAN-approved workshops.

SIGPLAN-approved workshops must respect the SIGPLAN Diversity Policy. Proposals for SIGPLAN-approved workshops must additionally include the gender, country of affiliation, and professional status of potential PC members. See https://www.sigplan.org/Resources/Policies/Diversity/ for more details.

---------------------------------------------------------------------

Selection committee

All submissions will be evaluated by a committee comprising the workshops co-chairs, the general chair, and the program chair.

---------------------------------------------------------------------

Further information

Any questions regarding POPL 2025 co-located event proposals should be addressed to the workshops chairs Christoph Matheja (chmat@dtu.dk) and Robert Rand (rand@uchicago.edu).

Posted by at No comments:

2024-06-11

[Caml-list] Attn: Development Editor, Latest OCaml Weekly News

OCaml Weekly News

Previous Week Up Next Week

Hello

Here is the latest OCaml Weekly News, for the week of June 04 to 11, 2024.

Providing Opam system dependancies with Nix

Archive: https://discuss.ocaml.org/t/providing-opam-system-dependancies-with-nix/14745/1

Ryan announced

I've opened a PR with input from @dra27 and @avsm adding support for Nix depexts (system dependencies) to Opam.

Opam supports system dependencies for other platforms by invoking the system package manager, e.g. apt-get install .... However Nix is a bit different, as in general installing a package to your system doesn't create the development environment required to use it; it will only add executables to your $PATH. To find, for example, objects files, outside of a Nix derivation you can use nix-shell and it's descendant nix develop. E.g.: 

  $ nix-shell -p gmp  $ echo $NIX_LDFLAGS  -rpath /nix/store/20g5iw2r512gnfrdr4imp2y940v3vlif-shell/lib  -L/nix/store/rx6nkd40819acppajq29g1hxa4d9r35f-gmp-with-cxx-6.3.0/lib -L/nix/store/rx6nkd40819acppajq29g1hxa4d9r35f-gmp-with-cxx-6.3.0/lib

We support Nix depexts with Opam in a similar way. A Nix derivation is build with the desired packages as inputs, and the resulting environment is output as a file in the Opam switch in a format that Opam can parse. This nix.env file is a symlink into the Nix store, so acts as a garbage collection root – packages won't be removed from the store while this file exists. Opam outputs these environment variables on an invocation of opam env.

This fixes issues such as https://discuss.ocaml.org/t/opam-and-nixos-is-there-an-alternative-to-nix-shell/13726.

While the primary use case is on NixOS, this depext mechanism could be used on other platforms to provide a consistent experience including other Linux distributions, BSDs, (and possibly even windows in the future).

Nixpkgs typically only packages one version of a package at a time, but I'm working on versioned depexts with previous version of Nixpkgs as outlined here.

I'm keen to get people's opinions and perspective on this!

ppx_deriving.6.0.2 and ppx_deriving_yojson.3.8.0

Archive: https://discuss.ocaml.org/t/ann-ppx-deriving-6-0-2-and-ppx-deriving-yojson-3-8-0/14750/1

Nathan Rebours announced

I am happy to announce the release of ppx_deriving.6.0.2 and ppx_deriving_yojson.3.8.0, the first release of those packages in years!

The main feature here is the port of ppx_deriving's standard derivers ([@@deriving show, make, ord, eq, ...]) and ppx_deriving_yojson to ppxlib's Deriving api. There are no changes to how you'd use those derivers but many benefits:

  • Better performances and better integration with other ppx-es as the code is now generated as part of ppxlib's driver main AST rewriting phase rather than in a separate, dedicated phase.
  • They can now be used with [@@deriving_inline]
  • None of them will break the location invariant required by merlin anymore, fixing a long lasting bug and providing a much better user experience.

You can find the full release notes for ppx_deriving here and for ppx_deriving_yojson here.

I'd like to thank @sim642 for all their work on the ppxlib ports and their patience, and all our other contributors.

I'd also like to thank the OCaml Software Foundation who has been funding my work on those releases.

Effective ML Through Merlin's Destruct Command

Archive: https://discuss.ocaml.org/t/blog-effective-ml-through-merlins-destruct-command/14751/1

Xavier Van de Woestyne announced

I'm very pleased to present you an article with a collection of small illustrations and examples of how to use the destruct command to generate patterns in the presence of pattern matches.

The command has been present in Merlin for several years (and accessible via OCaml-LSP) but, as the various changelogs relating to Merlin mention, we have spent some time polishing it and adapting it to the evolutions of OCaml, making it more stable (essentially in the presence of punning) and taking into account the changes made to the representation of functions (and their parameters).

The aim of the article is to show how the destruct command works in a number of very concrete cases, and ends with an example (a little artificial for the purposes of the article and for teaching purposes) which shows how to use destruct interactively.

Can't wait to hear your feedback! Happy reading!

OCaml Windows Working Group

Archive: https://discuss.ocaml.org/t/ocaml-windows-working-group/14755/1

Sudha Parimala announced

I'm happy to share that we're starting a working group for OCaml Windows. This is part of a larger effort, First-class Windows, to enhance the OCaml experience on Windows. Through this effort, we aim to coordinate our collective knowledge to identify high-priority items for First-class Windows.

We've started a mailing list to exchange ideas and would greatly appreciate inputs. You can sign up at – https://groups.google.com/u/0/g/ocaml-windows-wg

While the mailing list is intended to be the primary means of communication, we plan to do a sync meeting once a month, to start with. We plan to do a kick-off meeting early next week. Please fill in this poll if you're interested to join: https://strawpoll.com/polls/PbZqbmkNeyN.

Happy camling :camel:

Flambda2 Ep. 2: Loopifying Tail-Recursive Functions, by OCamlPro

Archive: https://discuss.ocaml.org/t/blog-flambda2-ep-2-loopifying-tail-recursive-functions-by-ocamlpro/14758/1

OCamlPro announced

Greetings Cameleers,

We would like to share with you our latest Flambda2 Snippet: Flambda2 Ep. 2: Loopifying Tail-Recursive Functions!

Indeed, today's topic is what is called Loopify, one of the many optimisation algorithms found in the Flambda2 optimising compiler project.

We believe Loopify is a nicely representative piece of software for our readers to grasp at the general design and philosophy for all optimisations available in Flambda2! Hopefully, you will do too!

Be sure to check out the Flambda2 Ep.0 article to get all the context for the project itself and the series of blog posts!

In any case, we await your feedback below, and hope that you will enjoy reading this post, and all ensuing ones!

Kind regards, The OCamlPro Team

OCaml Platform Newsletter: March-May 2024

Archive: https://discuss.ocaml.org/t/ocaml-platform-newsletter-march-may-2024/14765/1

Thibaut Mattio announced

Welcome to the eleventh edition of the OCaml Platform newsletter!

In this March-May 2024 edition, we are excited to bring you the latest on the OCaml Platform, continuing our tradition of highlighting recent developments as seen in previous editions. To understand the direction we're headed, especially regarding development workflows and user experience improvements, check out our roadmap.

Highlights:

  • Explorations on Dune package management have reached a Minimal-Viable-Product (MVP) stage: a version of Dune that can build non-trivial projects like OCaml.org and Bonsai. With a working MVP, the team is shifting their focus to putting Dune package management in the hands of the community. To that end, we have started the Dune Developer Preview Program, where we will test Dune package management with users and refine the user experience in preparation for a final release.
  • The opam team released a second beta of opam 2.2, and with it, opened the final PR to add support for Windows OCaml to the opam-repository. Once the PR is merged, opam 2.2 will be usable with the upstream opam-repository on Windows, paving the way for a third beta very soon, and a Release Candidate next.
  • The odoc team has finalized the initial design for Odoc 3.0 and opened several RFCs to gather community input. We've implemented a new Odoc driver that follows the Odoc 3.0 design and have already started prototyping key parts of the design.
  • Merlin's project-wide references query is getting very close to release. The necessary compiler PR has been merged and included in OCaml 5.2, and the Dune rules PR has been merged and included in Dune 3.16. The next steps are to merge the PR in Merlin itself and the small patch in OCaml LSP.
  • The set of standard derivers shipped with ppx_deriving.std (i.e. [@@deriving show, make, ord, eq, ...]) as well as ppx_deriving_yojson are now directly written against Ppxlib's API. That impacts developers in two ways. First, it allows you to enjoy reliable editor features in projects with those derivers (Ppxlib preserves Merlin's location invariants). Second, you can avoid a hard dependency on those derivers by using Ppxlib's deriving_inline feature on them. Thanks a lot to @sim642 for all your work and very kind patience, @NathanReb for reviewing and release managing, and everyone else involved!

Releases:

[Dune] Exploring Package Management in Dune (W4)

Contributed by: @rgrinberg (Tarides), @Leonidas-from-XIV (Tarides), @gridbugs (Tarides), @Alizter

Why: Unify OCaml tooling under a single command line for all development workflows. This addresses one of the most important pain points reported by the community.

What: Prototyping the integration of package management into Dune using opam as a library. We're introducing a dune pkg lock command to generate a lock file and enhancing dune build to handle dependencies in the lock file. More details in the Dune RFC.

Summary:

Over the past three months, significant progress has been made in adding Dune's support for package management. We are thrilled to report that our prototypes have reached a Minimal Viable Product (MVP) stage: an experimental version of Dune package management that can be used to build non-trivial projects, including OCaml.org and Bonsai, which we are using in our tests.

There is still a long way to go, but with this milestone reached, we are now shifting our focus from prototyping to putting the feature in the hands of the community. We are moving to testing the new Dune feature with users, and in particular, now that we have a good understanding of the technical blockers and their workarounds, we will be focusing on validating and refining the developer experience (DX) of Dune package management in preparation for a first release.

To that end, the Dune team has started a Dune Developer Preview Program. We're currently testing the Developer Preview of package management with selected beta testers, and once the biggest issues have been addressed, we'll be opening it to the broader community.

Activities:

[opam] Native Support for Windows in opam 2.2 (W5)

Contributed by: @rjbou (OCamlPro), @kit-ty-kate (Ahrefs), @dra27 (Tarides), @AltGr (OCamlPro)

Why: Enhance OCaml's viability on Windows by integrating native opam and opam-repository support, fostering a larger community, and more Windows-friendly packages.

What: Releasing opam 2.2 with native Windows support, making the official opam-repository usable on Windows platforms.

Summary:

The opam team is getting closer to a final release of opam 2.2 with support for Windows. In the past months, we have released a second beta of opam 2.2, addressing a number of issues reported by users on previous releases, including Windows issues.

Excitingly, we also opened the final PR adding support for Windows OCaml to opam-repository. With the PR merged, the opam team is expecting to be able to move to a Release Candidate in June.

Stay tuned for more exciting news and releases in the coming weeks and months!

Activities:

[​odoc​] Odoc 3.0: Unify OCaml.org and Local Package Documentation (W25)

Contributed by: @jonludlam (Tarides), @julow (Tarides), @panglesd (Tarides), Luke Maurer (Jane Street)

Why: Improving local documentation generation workflow will help package authors write better documentation for their packages, and consolidating the different odoc documentation generators will help make continuous improvements to odoc available to a larger audience.

What: We will create conventions that drivers must follow to ensure that their output will be functional. Once established, we will update the Dune rules to follow these rules, access new odoc features (e.g., source rendering), and provide similar functionalities to docs.ocaml.org (a navigational sidebar, for instance). This will effectively make Dune usable to generate OCaml.org package documentation.

Summary:

The Odoc team has made significant progress on the upcoming Odoc 3.0. We held productive in-person meetings in Paris to discuss crucial design aspects such as the CLI, source code rendering, and references. These discussions led to the publications of RFCs for the various components of the design specification.

We also started implementing a new Odoc driver that adheres to the new design for testing purposes, and began prototyping several of the new features.

While discussions on the RFCs and specific features are still ongoing, we are very excited to have a solid set of design specifications under community review and to have begun implementing key parts of the new design.

Activities:

[Merlin] Support for Project-Wide References in Merlin (W19)

Contributed by: @vds (Tarides), @Ekdohibs (OCamlPro), @Octachron (INRIA), @gasche (INRIA), @emillon (Tarides), @rgrinberg (Jane Street), @Julow (Tarides)

Why: Enhance code navigation and refactoring for developers by providing project-wide reference editor features, aligning OCaml with the editor experience found in other languages.

What: Introducing ocamlmerlin server occurrences and LSP textDocument/references support, extending compiler's Shapes for global occurrences and integrating these features in Dune, Merlin, and OCaml LSP.

Summary:

The past few months have seen fantastic progress on releasing Merlin's project-wide reference query: The compiler PR got merged and included in the now released OCaml 5.2; The Dune rules PR got merged, and with it significant performance improvements have been made on the indexing tool. The final PR in Merlin is open and under review. That PR as well as the small LSP patch to support the feature are about to be merged.

The PR on Merlin also adds support for the feature in the Merlin server plug-in for Emacs. Support for the Merlin server plug-in for Vim has been added separately. All editor plug-ins based on LSP will support the new feature automatically.

Activities:

  • We followed up on our compiler PR to improve performance for shape aliases weak reduction. It got merged, and made it into OCaml 5.2.0. – ocaml/ocaml#13001
  • We improved the Dune rules that drive the indexer: Simplified the rules, added benchmarks, discussed and improved performance. The PR got merged, and made it into Dune 3.16. - ocaml/dune#10422
  • We polished the indexer ocaml-index: Profiled it and improved its speed by a factor ~2, and improved its CLI.
  • We added a :MerlinOccurrencesProjectWide command to the Vim plug-in based on the Merlin server - ocaml/merlin#1767

OCaml.org Newsletter: May 2024

Archive: https://discuss.ocaml.org/t/ocaml-org-newsletter-may-2024/14767/1

Sabine Schmaltz announced

Welcome to the May 2024 edition of the OCaml.org newsletter! This update has been compiled by the OCaml.org team. You can find previous updates on Discuss.

Our goal is to make OCaml.org the best resource for anyone who wants to get started and be productive in OCaml. The OCaml.org newsletter provides an update on our progress towards that goal and an overview of the changes we are working on.

We couldn't do it without all the amazing people who help us review, revise, and create better OCaml documentation and work on issues. Your participation enables us to so much more than we could just by ourselves. Thank you!

This newsletter covers:

  • Recipes for the OCaml Cookbook: Help us make the OCaml Cookbook really useful by contributing and reviewing recipes for common tasks!
  • Community & Marketing Pages Rework: We have UI designs for the reworked and new pages of the community section and are starting to implement these. We made progress towards showing videos from the community on the OCaml Planet.
  • General Improvements: As usual, we also worked on general maintenance and improvements, so we're highlighting some of the work that happened below.

Recipes for the OCaml Cookbook

The OCaml Cookbook is a place where OCaml developers share how to solve common tasks using packages from the ecosystem.

A recipe is a code sample and explanations on how to perform a task using a combination of open source libraries.

The Cookbook is live at ocaml.org/cookbook, but there are not a lot of recipes published yet.

When the cookbook was merged, all pull requests to the cookbook branch were automatically closed. We recreated these pull requests and they are ready for review.

Here's how you can help:

  1. Review open pull requests for cookbook recipes!
  2. Contribute new recipes and tasks for the cookbook!

Relevant PRs and Activities:

Community & Marketing Pages Rework

This month, we made some progress towards adding videos from the OCaml community (e.g., from YouTube and watch.ocaml.org) to the OCaml Planet.

Since the size of the OCaml Planet RSS feed grew so large that automation tools (dlvr.it) could no longer process it, we reduced the timeframe for posts to show up in the RSS feed to the last 90 days.

Contributor @ishar19 opened a pull request to add an RSS feed for the Community/Events page. This will allow posting new events to various social media automatically and allow you to subscribe to the Events RSS feed with a RSS reader of your choice.

We have UI designs for the reworked and new pages of the community section and we are opening small issues for contributors to help. :orange_heart:

Relevant PRs and Activities:

Outreachy Internship on Interactive Exercises

On May 27, Divyanka Chaudhari started working with the team, as an Outreachy intern. She's implementing support for running the exercises as a stand-alone project, either in GitHub Codespace, in repl.it, using Jupyter or LearnOcaml.

Relevant PRs and Activities:

## General Improvements and Data Additions

Notable Changes:

  • We restructured the main navigation to have a "Tools" section that holds the OCaml Platform page and the OCaml compiler releases page. This should make the OCaml Platform page easier to find.
  • The Changelog can now be found under "News", from the main navigation. You can also find the OCaml Planet and the Newsletters in this new section.
  • The OCaml Language Manual is now served from OCaml.org, instead of v2.ocaml.org.
  • We added some more links to learning resources to the Resources page at https://ocaml.org/resources.
  • Some documentation updates on "Is OCaml Web Yet?", "Is OCaml GUI Yet?", the ThreadSanitizer tutorial, and the "Functors" tutorial.

Relevant PRs and Activities:

OCaml Windows Working Group

Archive: https://discuss.ocaml.org/t/ocaml-windows-working-group/14755/3

Deep in this thread, Sudha Parimala announced

Thanks to everyone who joined the meeting! Please find the notes here: https://docs.google.com/document/d/1tt-g5f441ClvdGJuK8fvO9Eu2YvWMwDF1wbZ2f8-gsI/edit#heading=h.kwwpagbnenby.

The meeting time this time wasn't US time-zone friendly. We'll try to find a time that works for more people next time.

Registration for Fun OCaml 2024 Opens Shortly

Archive: https://discuss.ocaml.org/t/registration-for-fun-ocaml-2024-opens-shortly/14771/1

Sabine Schmaltz announced

Registration for Fun OCaml 2024 will open shortly at 17:00 CEST (Central European Summer Time) UTC/GMT +2 hours

Please put yourself on the waiting list if you don't get a ticket immediately, we're doing this in a staggered fashion, unlocking more tickets over the next days! 🧡🐫

https://fun-ocaml.com

opam 2.2.0~beta3

Archive: https://discuss.ocaml.org/t/ann-opam-2-2-0-beta3/14772/1

Kate announced

We're once again very excited to announce this third and final beta for opam 2.2.0.

What's new in this beta?

  • opam init on Windows enhancements: this beta greatly improves the opam init user experience on Windows, and the number of recognised configurations
  • opam init –cygwin-extra-packages=\<pkgs\>: a new argument to specify additional packages for the internal Cygwin installation
  • Support of user directories containing spaces: opam now redirects the opam root to C:\opamroot\opam-xxx when the opam root contains spaces on Windows
  • UTF-8 paged –help on Windows thanks to cmdliner 1.3.0 and some additional Windows API calls, all the opam --help commands now display a paged view by default similar to Unix-like systems.
  • Many fixes, performance and general improvements

:open_book: You can read our blog post for more information about these changes and more, and for even more details you can take a look at the release note or the changelog.

Windows issues

Configuration of Windows is tricky, so please don't be too disheartened if things don't work instantly. If something doesn't work first time, please do report it, even if you manage to find a way to workaround it. If opam didn't elegantly tell you what was wrong, then it's a bug and we'd love to hear about it, rather than ending up with a series of workarounds flying around. It's no problem at all for us to receive a bug report which turns out to be user error - we'd far rather that than not hear bugs which are opam's error! 🙀

How to upgrade

  • On Windows

    BEWARE: the command shown below is experimental, use caution and please do report any issues that you are experiencing. If you prefer to not use our experimental script, feel free to get the Windows binary directly from the Release Page and put it in your directory of choice instead.

    Now that the Windows support was merged in opam-repository,

    installing opam is as simple as calling the following command from a PowerShell terminal: 

      Invoke-Expression "& { $(Invoke-RestMethod https://raw.githubusercontent.com/kit-ty-kate/opam/windows-installer/shell/install.ps1) }"

    opening a new terminal, and a simple opam init will work out-of-the-box.

  • On Unix-like systems

    To upgrade, simply run: 

      bash -c "sh <(curl -fsSL https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh) --version 2.2.0~beta3"

    We're planning for an opam 2.2.0~rc1 release later next week, so please do report any issue you encounter on our bug-tracker.

Other OCaml News

Old CWN

If you happen to miss a CWN, you can send me a message and I'll mail it to you, or go take a look at the archive or the RSS feed of the archives.

If you also wish to receive it every week by mail, you may subscribe to the caml-list.

Posted by at No comments:

2024-06-04

[Caml-list] [Deadline extention] ML 2024 – Call for presentations: ACM SIGPLAN ML Family Workshop

Dear all,

We extended the deadline for presentation proposals at the ML workshop (@ ICFP 2024) to June 14th.

If you cannot join us in Milan, remote presentations are also possible.

Please find the complete CFP below.

Best regards,

Guillaume Munch-Maccagnoni



We are happy to invite submissions to ML 2024 (apologies for cross-postings).

  * Submission deadline: June 14th
  * September 6th in Milan, Italy. Co-located with ICFP 2024.
  * Submission website: https://ml2024.hotcrp.com   * Workshop website: https://icfp24.sigplan.org/home/mlworkshop-2024

# Higher-order, Typed, Inferred, Strict: ACM SIGPLAN ML Family Workshop

ML (originally, "Meta Language") is a family of programming languages
that includes dialects known as Standard ML, OCaml, and F#, among
others. The development of these languages has inspired a large amount
of computer science research, both practical and theoretical.

The ML Family Workshop is an established informal workshop aiming to
recognize the entire extended ML family and to provide the forum to
present and discuss common issues: all aspects of the design,
semantics, theory, application, implementation, and teaching of the
members of the ML family. We also encourage presentations from related
languages (such as Haskell, Scala, Rust, Nemerle, Links, Koka, F*,
Eff, ATS, etc), to promote the exchange of ideas and experience. The
ML family workshop will be held in close coordination with the OCaml
Users and Developers Workshop.

## Format

The ML 2024 workshop will continue the informal approach followed
since 2010. Presentations are selected by the program committee from
submitted proposals. There are no published proceedings, so
contributions may be submitted for publication elsewhere. The main
criterion is the promoting and informing the development of the entire
extended ML family and delivering a lively workshop atmosphere. We
particularly encourage talks about works in progress, presentations of
negative results (things that were expected to but did not quite work
out) and informed positions.

Each presentation should take 20-25 minutes. The exact time will be
decided based on scheduling constraints.

We plan the workshop to an be in-person event with remote
participation (streamed live). Speakers are generally expected to
present in person (we will work to make remote presentations
possible).

The 2024 ML family workshop is co-located with ICFP 2024 and will take
place on September the 6th in Milan, Italy.

## Scope

We seek presentations on topics including (but not limited to):

* Language design: abstraction, higher forms of polymorphism,
 concurrency, distribution and mobility, staging, extensions for
 semi-structured data, generic programming, object systems, etc.

* Implementation: compilers, interpreters, type checkers, partial
 evaluators, runtime systems, garbage collectors, foreign function
 interfaces, etc.

* Type systems: inference, effects, modules, contracts, specifications
 and assertions, dynamic typing, error reporting, etc.

* Applications: case studies, experience reports, pearls, etc.

* Environments: libraries, tools, editors, debuggers, cross-language
 interoperability, functional data structures, etc.

* Semantics of ML-family languages: operational and denotational
 semantics, program equivalence, parametricity, mechanization, etc.

We specifically encourage reporting what did not meet expectations or
what, despite all efforts, did not work to satisfaction.

Four kinds of submissions are solicited: Research Presentations,
Experience Reports, Demos, and Informed Positions.

* Research Presentations: Research presentations should describe new
 ideas, experimental results, or significant advances in ML-related
 projects. We especially encourage presentations that describe work
 in progress, that outline a future research agenda, or that
 encourage lively discussion. These presentations should be
 structured in a way which can be, at least in part, of interest to
 (advanced) users.

* Experience Reports: Users are invited to submit Experience Reports
 about their use of ML and related languages. These presentations do
 not need to contain original research but they should tell an
 interesting story to researchers or other advanced users, such as an
 innovative or unexpected use of advanced features or a description
 of the challenges they are facing or attempting to solve.

* Demos: Live demonstrations or short tutorials should show new
 developments, interesting prototypes, or work in progress, in the
 form of tools, libraries, or applications built on or related to ML
 and related languages. (You will need to provide all the hardware
 and software required for your demo; the workshop organizers are
 only able to provide a projector.)

* Informed Positions: A justified argument for or against a language
 feature. The argument must be substantiated, either theoretically
 (e.g., by a demonstration of (un)soundness, an inference algorithm,
 a complexity analysis), empirically or by substantial experience.
 Personal experience is accepted as justification so long as it is
 extensive and illustrated with concrete examples.

## Submission details

Submissions must be in the PDF format and have a short summary
(abstract) at the beginning. Submissions in the categories of
Experience Reports, Demos, or Informed Positions should indicate so in
the title or subtitle. The point of the submission should be clear
from its two first pages (PC members are not obligated to read any
further.)

Submissions must be uploaded to the workshop submission website before
the submission deadline.

Only the short summary/abstract of accepted submissions will be
published on the conference website. After acceptance, authors will
have the opportunity to attach or link to that summary any relevant
material (such as the updated submission, slides, etc.)

*Submission website*: https://ml2024.hotcrp.com/
*Workshop website*: https://icfp24.sigplan.org/home/mlworkshop-2024
## Coordination with the OCaml Users and Developers Workshop

The OCaml workshop is seen as more practical and is dedicated in
significant part to OCaml community building and the development of
the OCaml system. In contrast, the ML family workshop is not focused
on any language in particular, is more research-oriented, and deals
with general issues of ML-style programming and type systems. Yet
there is an overlap, which we are keen to explore in various ways. The
authors who feel their submission fits both workshops are encouraged
to mention it at submission time or contact the program chairs. 


--   Guillaume Munch-Maccagnoni  Researcher at INRIA  Gallinette team, Nantes  https://guillaume.munch.name/
Posted by at No comments:

2024-05-24

[Caml-list] PLMW@ICFP'24: Call for Participation (travel funding application by June 21)

ACM SIGPLAN Programming Languages Mentoring Workshop (PLMW) at ICFP 24, Milan, Italy

Workshop: Monday, September 2, 2024
Website: https://icfp24.sigplan.org/home/PLMW-ICFP-2024

PLMW is a workshop co-located with ICFP 2024 (the International Conference on Functional Programming) in Milan, Italy, from September 2-7.

The purpose of this mentoring workshop is to encourage graduate students and senior undergraduate students to pursue careers in programming language research. This workshop will bring together world leaders in programming languages research and teaching from academia and industry to help students imagine how they might contribute to our research community. Topics will range from the abstract (e.g., what is PL research and how does one become involved in it) to the concrete (e.g., how to navigate an academic conference, how to pick a research area) as well as technical talks on cutting-edge topics.

We especially encourage women and underrepresented minority students, and people with disabilities to attend PLMW.

This workshop is part of the activities surrounding ICFP, and takes place the day before the main conference. One goal of the workshop is to make the ICFP conference more accessible to newcomers. We hope that participants will stay through the entire conference.

Note that ICFP and PLMW are planned to be largely in-person events. While we recognize that travel to conferences is not easy for everyone, we do hope you will be able to join us in person to get the most out of the conference and its community-building aspects.

A number of sponsors have generously donated scholarship funds for qualified students to attend PLMW. These scholarships can cover expenses (airfare, hotel, and registration fees) for attendance at both the workshop and the ICFP conference.

Students attending this year will get one year free student membership of SIGPLAN, unless they prefer to opt out during their application.

The workshop registration is open to all. Students with alternative sources of funding are welcome as well.

—--------------------------------------------------------------

APPLICATION FOR PLMW TRAVEL FUNDING

For full consideration for scholarship funding, please apply at the link below by June 21, AoE. We will notify accepted attendees in a rolling fashion until all funding is committed.

The application can be accessed at the following URL  (Apply by June 21, 2024 AOE for full consideration!):
https://forms.gle/vC6udnMWRvvAczPR6
Posted by at No comments:

2024-05-20

[Caml-list] POPL 2025: First Call for Papers (deadline: July 11 AOE)

Dear all,

Please find below the Call for Papers for the POPL 2025 conference. We would be grateful if you could help distribute this call among your networks.

Many thanks!

Ningning Xie
POPL 2025 Publicity Chair

PACMPL Issue POPL 2025 seeks contributions on all aspects of programming languages and programming systems, both theoretical and practical. Authors of papers published in PACMPL Issue POPL 2025 will be invited to present their work in the POPL conference in January 2025, which is sponsored by ACM SIGPLAN, in cooperation with ACM SIGACT and ACM SIGLOG.

POPL 2025 Website: https://conf.researchr.org/home/POPL-2025

Call for Papers: https://conf.researchr.org/track/POPL-2025/POPL-2025-popl-research-papers#POPL-2025-Call-for-Papers

Double-Blind Review FAQ: https://conf.researchr.org/track/POPL-2025/POPL-2025-popl-research-papers#FAQ-on-Double-Blind-Reviewing


### Organization

Conference Location: Denver, Colorado, United States

Conference Dates: January 19-25, 2025

General Chair: Steve Zdancewic, University of Pennsylvania

Program Chair: Armando Solar-Lezama, MIT

Program Committee: https://conf.researchr.org/committee/POPL-2025/POPL-2025-popl-research-papers-program-committee


### Important Dates

All the times/deadlines below are Anywhere on Earth (AoE) in 2024.

Submission deadline: July 11


### Scope

Principles of Programming Languages (POPL) is a forum for the discussion of all aspects of programming languages and programming systems. Both theoretical and experimental papers are welcome, on topics ranging from formal frameworks to experience reports. We seek submissions that make principled, enduring contributions to the theory, design, understanding, implementation, or application of programming languages.


### Evaluation Criteria

The Review Committee will evaluate the technical contribution of each submission as well as its accessibility to both experts and the general POPL audience. All papers will be judged on significance, originality, relevance, correctness, and clarity. Each paper must explain its scientific contribution in both general and technical terms, identifying what has been accomplished, explaining why it is significant, and comparing it with previous work. Advice on writing technical papers can be found on the SIGPLAN author information page: https://www.sigplan.org/Resources/Author/.

Deadlines and formatting requirements, detailed below, will be strictly enforced.


### Double-Blind Reviewing Process

POPL 2025 will use a full double-blind reviewing process (similar to the one used for POPL 2023 and 2024 but different from the lightweight double-blind process used in previous years). This means that identities of authors will not be made visible to reviewers until after conditional-acceptance decisions have been made, and then only for the conditionally-accepted papers. The use of full double-blind reviewing has several consequences for authors.

* **Submissions**: Authors must omit their names and institutions from their paper submissions. In addition, references to authors' own prior work should be in the third person (e.g., not "We build on our previous work …" but rather "We build on the work of …").

* **Supplementary material**: Authors are permitted to provide supplementary material (e.g., detailed proofs, proof scripts, system implementations, or experimental data) along with their submission, which reviewers may (but are not required to) examine. This material may take the form of a single file, such as a PDF or a tarball. Authors must fully anonymize any supplementary material.

* **Author response**: In responding to reviews, authors should not say anything that reveals their identity, since author identities will not be revealed to reviewers at that stage of the reviewing process.

* **Dissemination of work under submission**: Authors are welcome to disseminate their ideas and post draft versions of their paper(s) on their personal website, institutional repository, or arXiv (reviewers will be asked to turn off arXiv notifications during the review period). But authors should not take steps that would almost certainly reveal their identities to members of the Program Committee, e.g., directly contacting PC members or publicizing the work on widely-visible social media or major mailing lists used by the community.

The purpose of the above restrictions is to help the Program Committee and external reviewers come to a judgment about the paper without bias, not to make it impossible for them to discover the authors' identities if they were to try. In particular, nothing should be done in the name of anonymity that weakens the quality of the submission.

However, there are occasionally cases where adhering to the above restrictions is truly difficult or impossible for one reason or another. In such cases, the authors should contact the Program Chair to discuss the situation and how to handle it.

The FAQ on Double-Blind Reviewing addresses many common scenarios and answers many common questions about this topic. But there remain many grey areas and trade-offs. If you have any doubts about how to interpret the double-blind rules or you encounter a complex case that is not clearly covered by the FAQ, please contact the Program Chair for guidance.

### Evaluation Process

Like last year, POPL 2025 will use a double-blind reviewing process (instead of the lightweight double-blind process used in recent years). This means that identities of authors will not be visible to reviewers until after conditional-acceptance decisions have been made. For authors, the main change is that there is no option to upload non-anonymized supplementary material; only anonymized supplementary material may be submitted.

POPL 2025 will have five Associate Chairs who will help the PC Chair monitor reviews, solicit external expert reviews for submissions when there is not enough expertise on the committee, and facilitate reviewer discussions.

As in previous years, authors will have a multi-day period to respond to reviews, as indicated in the Important Dates table. Responses are optional. A response must be concise, addressing specific points raised in the reviews; in particular, it must not introduce new technical results. Reviewers will write a short reaction to these author responses.

The Review Committee (RC) will discuss papers electronically, and will use synchronous virtual meetings to discuss any papers for which there is disagreement among reviewers, in some cases soliciting additional input from other experts in the committee. There is no formal External Review Committee, though experts outside the committee may be consulted for some papers. Reviews will be accompanied by a short summary of the reasons behind the committee's decision with the goal of clarifying the reasons behind the decision.

To conform with ACM requirements for journal publication, all POPL papers will be conditionally accepted; authors will be required to submit a short description of the changes made to the final version of the paper, including how the changes address any requirements imposed by the Review Committee. That the changes are sufficient will be confirmed by the original reviewers prior to acceptance to POPL. Authors of conditionally accepted papers must submit a satisfactory revision to the Review Committee by the requested deadline or risk rejection.

For additional information about the reviewing process, see: [Principles of POPL](https://www.sigplan.org/Conferences/POPL/Principles/), a presentation of the underlying organizational and reviewing policies for POPL. For POPL 2025, policies specified in this Call for Papers supersede those in the Principles of POPL document.


### Submission Site Information

The submission site is https://popl25.hotcrp.com.

Authors can submit multiple times prior to the deadline. Only the last submission will be reviewed. There is no abstract deadline. The submission site requires entering author names and affiliations, relevant topics, and potential conflicts. Addition or removal of authors after the submission deadline will need to be approved by the Program Chair (as this kind of change potentially undermines the goal of eliminating conflicts during paper assignment).

The submission deadline is 11:59PM July 11, 2024 anywhere on earth: https://en.wikipedia.org/wiki/Anywhere_on_Earth


### Conflicts of Interest

For each submission, the authors must make sure that they properly declare all potential conflicts of interest for all of the authors of that submission. This includes marking PC conflicts as well as "Other Conflicts (external)". A conflict caught late in the reviewing process leads to a voided review which may be infeasible to replace.

Conflicts should be declared between an adviser and an advisee (e.g., Ph.D., post-doc; forever), between an author and a co-author (papers and proposals; for two years), between people at the same institution (branches of large companies or different locations of research institutes are considered to be the same institution; for two years after leaving an institution), between people with financial conflicts of interest, and between friends or relatives.

Please do not declare spurious conflicts: such incorrect conflicts are especially harmful if the aim is to exclude potential reviewers, so spurious conflicts can be grounds for rejection. If you are unsure about a conflict, please consult the Program Chair.

### Submission Guidelines

Prior to the paper submission deadline, authors should upload their full anonymized paper. Here are some key requirements concerning paper submissions:

* Each paper should have no more than **25 pages of text, excluding bibliography**, using the PACMPL format (specifically, the `acmart` LaTeX class with `acmsmall` option). It is a single-column page layout with a 10 pt font, 12 pt line spacing, and wider margins than recent POPL page layouts. In this format, the main text block is 5.478 in (13.91 cm) wide and 7.884 in (20.03 cm) tall. Use of a different format (e.g., smaller fonts or a larger text block) is grounds for summary rejection. The PACMPL template for LaTeX can be found at the [SIGPLAN author information page](https://www.sigplan.org/Resources/Author/), and further information about PACMPL submissions can be found on the [PACMPL author guidelines page](https://dl.acm.org/journal/pacmpl/author-guidelines). PACMPL does not support submissions in Microsoft Word.

* We strongly encourage use of the `review` and `screen` options in order to make submissions easier to review.

* (**NEW this year**) Authors may choose which citation format they wish to use, which can be either author-year (the mandate for final versions in previous years) or numeric.

* Submissions should be in PDF and printable on both US Letter and A4 paper. Papers may be resubmitted to the submission site multiple times up until the deadline, but the last version submitted before the deadline will be the version reviewed.

* Submitted papers must adhere to the [SIGPLAN Republication Policy](https://www.sigplan.org/Resources/Policies/Republication/) and the [ACM Policy on Plagiarism](https://www.acm.org/publications/policies/plagiarism-overview). Concurrent paper submissions to other conferences, workshops, journals, or similar forums of publication are not allowed.

* Authors are free to submit supplementary material along with their submissions, but it must be fully anonymized.

* Authors must list all their conflicts of interest (both PC conflicts and external conflicts) in the HotCRP submission form.

* Authors may include additional information in a field of the HotCRP submission form labeled "Confidential Comments for the Program Chair". This information need not be anonymized. It can be used to inform the Program Chair, for example, about sensitive issues concerning a conflict with a PC member or about supplementary material that cannot be anonymized. It is left to the discretion of the Program Chair what to do with this information.

* If for some reason an author feels uncomfortable discussing a sensitive issue with the Program Chair (or communicating via the "Confidential Comments" field in HotCRP), they should feel free to get in touch instead with any of the Associate Chairs, with whom they can discuss the issue in confidence.

* Submissions from PC members (except the Program Chair) are permitted and will not be handled any differently than other submissions. This is in accordance with a recent change in policy approved by the SIGPLAN Executive Committee: SIGPLAN conferences that use full double-blind review and whose PCs have at least 50 members need not hold PC submissions to a higher standard.

### Artifact Evaluation for Accepted Papers

Authors of conditionally accepted papers will be invited to formally submit supporting materials to the Artifact Evaluation process. Artifact Evaluation is run by a separate committee whose task is to assess how the artifacts support the work described in the papers. Artifact submission is strongly encouraged but voluntary and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully will receive a seal of approval printed on the papers themselves. Authors of accepted papers are encouraged to make these materials publicly available upon publication of the proceedings, by including them as "source materials" in the ACM Digital Library.

### Copyright, Publication, and Presentation

As a Gold Open Access journal, PACMPL is committed to making peer-reviewed scientific research free of restrictions on both access and (re-)use. Authors are strongly encouraged to support libre open access by licensing their work with the [Creative Commons Attribution 4.0 International (CC BY) license](https://creativecommons.org/licenses/by/4.0/), which grants readers liberal (re-)use rights.

Authors of accepted papers will be required to choose one of the following publication rights:

* Author licenses the work with a [Creative Commons license](https://creativecommons.org/), retains copyright, and (implicitly) grants ACM non-exclusive permission to publish (suggested choice).
* Author retains copyright of the work and grants ACM a non-exclusive permission to publish license.
* Author retains copyright of the work and grants ACM an exclusive permission to publish license.
* Author transfers copyright of the work to ACM.

These choices follow from ACM Copyright Policy and ACM Author Rights, corresponding to ACM's "author pays" option. While PACMPL may ask authors who have funding for open-access fees to voluntarily cover the article processing charge (currently, US$400), payment is not required for publication. PACMPL and SIGPLAN continue to explore the best models for funding open access, focusing on approaches that are sustainable in the long-term while reducing short-term risk.

All papers will be archived by the ACM Digital Library. Authors will have the option of including supplementary material with their paper. The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work.

Authors of accepted papers are required to give a short talk (roughly 25 minutes long) at the conference, according to the conference schedule. However, authors who cannot attend in person will be provided with some option for remote presentation, as well as some mechanism for remote interaction with conference participants.


### Distinguished Paper Awards

At most 10% of the accepted papers of POPL 2025 will be designated as Distinguished Papers. This award highlights papers that the Review Committee thinks should be read by a broad audience due to their relevance, originality, significance, and clarity. The selection of the distinguished papers will be made based on the final version of the paper and through an additional review process.
Posted by at No comments:
Subscribe to: Posts (Atom)