On Monday, 21 May 2018 at 18:53:19 UTC, Jonathan M Davis wrote:
writeln = "foo";
is legal, and it's dumb, but it hasn't mattered much in
practice. So, causing a bunch of code breakage in order to
disallow it is unlikely to go over well. It would also then
make getters and setters inconsistent in that setters would
require @property and getters wouldn't. How much that matters
is debatable, but it does make such a change less palatable.
[...]
Can't assignment to a function be fixed though? Are there any
cases where fixing that will cause problems for @property free
functions because they all must take more that one parameter i
assume.
It's quite a big wart so we don't have to fix all of @property at
least, but that should be fixed if fixing it does not crap on
UFCS and @property free functions.