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 22472 - Correct error message for invalid void return #13258

Merged
merged 1 commit into from
Nov 3, 2021

Conversation

MoonlightSentinel
Copy link
Contributor

The old error message (return expression expected) ignored the
possibility that void and noreturn expressions are moved into e0.
This caused misleading error messages when errors are detected after
the move, claiming that the expression found in the source code is
missing.

Small improvement to #13135 because this is more likely to happen for
noreturn functions.

@dlang-bot
Copy link
Contributor

Thanks for your pull request and interest in making D better, @MoonlightSentinel! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

  • My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
  • My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
  • I have provided a detailed rationale explaining my changes
  • New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.


If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close Bugzilla Severity Description
22472 regression Invalid error message for `void` return from non-`void` functions

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "stable + dmd#13258"

src/dmd/statementsem.d Outdated Show resolved Hide resolved
@MoonlightSentinel MoonlightSentinel force-pushed the noreturn/return-msg branch 2 times, most recently from c0fc147 to 3bba410 Compare November 3, 2021 13:53
The old error message (`return expression expected`) ignored the
possibility that `void` and `noreturn` expressions are moved into `e0`.
This caused misleading error messages when errors are detected after
the move, claiming that the expression found in the source code is
missing.

Small improvement to dlang#13135 because this is more likely to happen for
`noreturn` functions.
@dlang-bot dlang-bot merged commit b142905 into dlang:stable Nov 3, 2021
@MoonlightSentinel MoonlightSentinel deleted the noreturn/return-msg branch January 28, 2022 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants