--- Comment #4 from 2012-08-29 16:29:36 PDT ---
(In reply to comment #3)
> Why dangerous? Normal method invocations work, so why shouldn't UFCS work?

Having methods (what UFCS emulates) which implicitly create a copy of the
object and operate on that copy would be confusing. Both for the interface user
and the creator. The latter will be forgetting about the 'ref' while the former
will not expect 'o.whatever' to copy 'o' and call 'whatever' using that private
copy. Both issues would be bug sources.

Not introducing unsound features is easier than later removing them...

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to