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

Revert "fix Issue 22790 - ref-return-scope is always ref-return, scope, unless return-scope appear in that order " #13799

Merged
merged 1 commit into from
Mar 11, 2022

Conversation

MoonlightSentinel
Copy link
Contributor

Reverts #13691. The PR broke the test suite and some outstanding review by @dkorpel wasn't resolved

…nless ref-scope appears in that order (#13691)"

This reverts commit f443703.
@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
22790 enhancement ref-return-scope is always ref-return, scope, unless return-scope appear in that order

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 "master + dmd#13799"

@dlang-bot dlang-bot merged commit 14ea643 into master Mar 11, 2022
@dkorpel dkorpel deleted the revert-13691-iretscope branch March 11, 2022 09:27
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.

4 participants