Rust has stronger safety than Chapel overall. That is covered in the initial + - table.

Re use-after-free and unsafe blocks, I’ve heard of parallel programmers using ‘unsafe’ everywhere. Maybe they are doing it wrong. Even so, one should not assume that Rust completely removes the issue.

I’m the author of the article.

Of course C++ and Rust have very different safety properties. These icons are summary information & the article defines what each means. Rust programmers still deal with unsafe code (possibly in libraries) and still need to be aware of use-after-free being an issue.

Tagging @hpsf.bsky.social - we are excited to work together!

In this talk, speakers will introduce Chapel as a general-purpose, scalable parallel programming language; and demonstrate how it can help with CFD workflows through CHAMPS.

CHAMPS’ core is aimed at aerospace application, solving the URANS equations (time and spectral) with several turbulence models with transition and roughness for aero-icing and aeroelastic models, all available within CHAMPS.

Apps written in Chapel span various domains, including data analytics, biodiversity detection, hydrology, cosmology. One example, the largest application developed using Chapel, is the CFD solver CHAMPS (Chapel Multi-Physics Software) in the laboratory of Prof. Laurendeau at Polytechnique Montreal.

Though Chapel code tends to be concise and readable, the resulting performance can compete with or beat standard high-performance computing (HPC) approaches, such as Fortran/C/C++, OpenMP, MPI, and/or CUDA.

Chapel promotes scalable parallelism, permitting code to be developed using a laptop’s multi-core processor, and then recompiled to run across the nodes and cores of a commodity cluster, cloud instance, or massive-scale supercomputer.

Abstract (in many small posts):

Chapel is a general-purpose programming language that makes parallel programming far more productive than conventional approaches.

Anyone can join!

Here is the link: www.nas.nasa.gov/pubs/ams/202...