Richard Carlsson

Make function application left associative so it can be chained

2

A point where Erlang has always broken the Principle of Least Astonishment is in function application. You would typically expect (particularly in a functional language) that if a function call...

Warn about alias patterns that unify constructors

3

It is currently allowed to write a pattern such as `{a,B}={Y,Z} -> ...` where both sides of the `=` are constructors. To track the variable bindings, the compiler and other...

Make assignment (match) in comprehension work as strict generator

7

Implements EEP 77 (https://github.com/erlang/eep/pull/74) It would be useful to be able to easily bind variables in the qualifiers of a comprehension, for example: ``` [Z || X

Simplify grammar of map/record update expressions

4

It has always been allowed to chain map updates as well as record updates, but the way this was expressed in the grammar was hardcoded and restrictive, and it was...

compiler: Enable warn_deprecated_catch by default

2

I think the warnings for deprecated catches should be turned on by default in OTP 29.

Correct the pretty-printing of `catch Expr`

1

In 3171f2b7 and 762a18aa the precedence levels used by `erl_pp` to format `catch Expr` was adjusted to avoid parentheses in many cases. However, this only works in situations where the...

Warn about variable exports from subexpressions

14

Except for "block structures" like case, receive, etc., there is really no good reason to allow variable bindings to be exported from a subexpression. It is very rarely done in...