Crystal 1.16.0 Is Released

Summary

We are announcing a new Crystal release 1.16.0 with several new features and bug fixes. Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions. Stats This release includes 162 changes since 1.15.1 by 19 contributors. We thank all the contributors for all the effort put into improving the language! ❤️ Changes Below we list the most remarkable changes in the language, compiler and stdlib. For more details, visit the full changelog. Breaking The following changes break prior behavior of the compiler, but we expect them to not break much in existing code. If this is not the case, please let us know in the issue tracker or forum. Fixed implementation of File.match? The implementation of File.match? was insufficient and has been replaced by a new algorithm. This change should not affect any behaviour that was previously working as documented. The correction of implementation bugs leads to the following changes in observed behaviour: Wildcard and globstar are able to match non-greedily. For example, **/a now matches a. Globstar matches full path segments only, otherwise it’s just two wildcards (which is equivalent to a single one). For example, a** no longer matches ab/c (but it matches ab). Subpatterns in branches are parsed with respect to their respective syntactical context. For example, {[}]} now matches }. It parses as a branch with one subpattern that describes the character set }. Previously, this was a parse error. Escapes for special character are recognized. For example, \\t now matches \t while previously it matched t. The grammar for parsing character classes is more flexible. For example, [a-], now matches a and -. Previously, it was a pattern error (incomplete character range). Note: Dir.glob is implemented differently and is not affected by that invalid behaviour. There were no changes to it. Thanks, @straight-shoota Parameter name suffixes are deprecated The suf...