A Simulation Using Sequential and Parallel Collections in Scala 2.13

Introduction

Software to be build is to compare data from independent satellite systems.  As fighter jets traverse airspace, each system determines its identity, recording the name of the jet type or an equivalent letter or number abbreviation. For data collected over time, the simulation software must ascertain whether systems agree on identification and if so, whether contrasting the data by single or multiple processors would be more efficient.

This article begins with a proof of concept in Scala 2.12.   A small program with function taking generic collection type parameters verifies the basic strategy.  The actual software is written in 2.13, in which generic collection types – those inheriting the GenTraversable hierarchy – have been deprecated [1].  The parallel package is also gone but can be brought back [2].

Scala 2.13: Has Scala Done it Again?

The release of Scala 2.13 had been in the works for quite a long time, but it was finally released last month. With the release of this version, there are quite a few changes that Scala has brought for the users.
The intent of this post is to explain some of the features Scala has introduced/improved since its previous version.

In this article, we focus on new features that Scala 2.13 has in store for users and whether you should migrate to Scala 2.13. I'll try to summarize all related knowledge in this blog, including documentation and the release notes as well.