--- Comment #10 from yebblies <> 2011-06-13 22:21:03 PDT ---
(In reply to comment #9)
> I don't understand. Elsewhere I have a bug report that asks for a new error
> message if you don't use the result of a pure function.
> But this bug report just asks for a better error message in the situation of
> using "return x;" in a void function. So I expected an error message like:
> foo.d(20): Error: a void function can't return 'int'.

Returning an int expression from a void function is perfectly legal, so long as
the expression has side effects.  This is explicitly allowed by the spec.

You're talking about two completely separate issues, both of which are
enhancements.  This issue is about providing a clearer error message without
changing the spec.

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

Reply via email to