Announcing Chapel 1.22!

[Brad C. <bra...@hp...>]

Dear Chapel community --

Cray, a Hewlett Packard Enterprise Company, and the Chapel open-source 
community are proud to announce the release of Chapel version 1.22!

This is the second of two Chapel releases that we are making this
month.  Last week's Chapel 1.21 was our typical semi-annual release
containing numerous feature and performance improvements, all of which
are part of Chapel 1.22 as well.

Today's Chapel 1.22 release focuses primarily on a single conceptual
change: that of making Chapel's implicitly indexed types use 0-based
rather than 1-based indexing.  This impacts tuples, strings, bytes,
lists, and inferred-type arrays that are not defined in terms ranges,
domains, or other arrays.  It also impacts language features and
library interfaces that are defined in terms of these types, such as
varargs functions, per-dimension queries of arrays, or search
functions on these types that return position values.

For a more in-depth description of these changes, how we got here, or
tips for updating existing Chapel programs to be compatible with 1.22,
please refer to:

       https://chapel-lang.org/docs/1.22/language/evolution.html

In addition, if you would like help updating to Chapel 1.22 and are
able to share your code with us, please don't hesitate to ask—we'd be
happy to help.

Beyond this major change, Chapel 1.22 also contains a few other
improvements in terms of memory leaks, documentation improvements, and
bug fixes.  For a more complete list of changes, including pointers to
supporting documentation, please refer to CHANGES.md within the
release or online:

   https://github.com/chapel-lang/chapel/blob/release/1.22/CHANGES.md

To download and install the release, see:

   https://chapel-lang.org/download.html

And for a list of everyone who contributed to Chapel 1.22, please see:

   https://github.com/chapel-lang/chapel/blob/release/1.22/CONTRIBUTORS.md

As always, we're interested in feedback on how we can make the Chapel
language, implementation, libraries, and tools more useful to you.

On behalf of the Chapel project,
-Brad Chamberlain


------------------------------------
For further information about Chapel
------------------------------------

Whether you're a user of Twitter or Facebook, or would simply enjoy
checking in on us from time-to-time, Chapel's social media pages have
a reasonably steady stream of content about the project and language:

    https://twitter.com/ChapelLanguage
    https://www.facebook.com/ChapelLanguage

Our development repository is hosted at GitHub, making it the best
place to track, or contribute to, ongoing Chapel development:

    https://github.com/chapel-lang/chapel

The Chapel website can be found at:

    https://chapel-lang.org

and it remains the best place to find Chapel-related information such
as videos, papers, presentations, blog posts, and tutorials.