On Thursday, 28 February 2013 at 13:06:39 UTC, Jacob Carlborg
wrote:
On 2013-02-28 09:21, deadalnix wrote:
Must is not appropriate here, as it isn't an obligation at
all. I don't
really see what is the concern here.
If the function is simple, then it will be inlined and unused
returned
values can be optimized away. If the function is complex, the
cost of
returning something when not needed will be negligible anyway.
What is your concern here ?
My concern here is setters that doesn't return a value. They
won't work with chained assignments. Another thing that will
break when changing a filed to a property.
That is up to the writer of the setter. Note that you can also
create getter that returns void. It is even more stupid. As long
as it isn't error prone.
