Make function application left associative so it can be chained

[richcarl]

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 returns another function, you can apply it directly by appending another set of arguments within parentheses, but in Erlang, you are also forced to put the first function call within an extra parenthesis, like so: (f(X))(Y), rather than the expected f(X)(Y). For example, (accessor(Path))(Thing). This can get tiresome when you're working with higher order functions, and sometimes actually obscures the fact that a function application is happening, due to the extra parentheses acting as camouflage.

The fix is easy, and since it has not been allowed before there is no existing code where this would change the meaning. It however required me to slightly refactor the remote_expr part of the grammar to fix conflicts. It turned out this could also easily be relaxed, so that you can write get_callback_module(State):callbackFunc(...) instead of the current (get_callback_module(State)):callbackFunc(...).

[github-actions]

CT Test Results

    2 files     96 suites   1h 7m 41s ⏱️
2 173 tests 2 125 ✅ 48 💤 0 ❌
2 536 runs  2 486 ✅ 50 💤 0 ❌

Results for commit d6dc8cf.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• Windows Installer

// Erlang/OTP Github Action Bot