Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix #29781, disallow spaces in broadcast calls #30182

Merged
merged 2 commits into from
Nov 29, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Merge branch 'master' into jb/fix29781
  • Loading branch information
JeffBezanson committed Nov 29, 2018
commit f61d56ac62f543675f28a4f8e3a3f5d71a21410e
5 changes: 3 additions & 2 deletions NEWS.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,11 @@ Language changes

* Parser inputs ending with a comma are now consistently treated as incomplete.
Previously they were sometimes parsed as tuples, depending on whitespace ([#28506]).
* `Regex` and `TimeZone` now behave like scalars when used in broadcasting ([#29913], [#30159]).
* `Char` now behaves like a read-only 0-dimensional array ([#29819]).
* Spaces were accidentally allowed in broadcast call syntax, e.g. `f. (x)`. They are now
disallowed, consistent with normal function call syntax ([#29781]).
* Big integer literals and command syntax (backticks) are now parsed with the name of
the macro (`@int128_str`, `@uint128_str`, `@big_str`, `@cmd`) qualified to refer
to the `Core` module ([#29968]).

New library functions
---------------------
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.