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 19105 - Bogus recursive template expansion via getS… #7158

Merged
merged 2 commits into from
Dec 1, 2019

Conversation

Biotronic
Copy link
Contributor

…ymbolsByUDA"

This reverts commit 86733d5.

Since PR 7100 did absolutely nothing to actually fix issue 19105 (it's a DMD issue, not a Phobos one), and instead disallows perfectly valid code, it should be reverted.

@Biotronic Biotronic requested a review from PetarKirov as a code owner August 28, 2019 12:02
@dlang-bot
Copy link
Contributor

dlang-bot commented Aug 28, 2019

Thanks for your pull request and interest in making D better, @Biotronic! 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
19105 normal Bogus recursive template expansion via getSymbolsByUDA
20054 regression getSymbolsByUDA no longer works on modules

Testing this PR locally

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

dub fetch digger
dub run digger -- build "stable + phobos#7158"

@thewilsonator
Copy link
Contributor

cc @RazvanN7

@PetarKirov
Copy link
Member

If I understand correctly, by reverting bug 20054 should also be fixed. Can you add a test for it in a separate commit?

@Biotronic
Copy link
Contributor Author

Done. However, this PR does not fix issue 19105. Is there some way I can tell the bot this?

@RazvanN7
Copy link
Collaborator

Squash your commits and make sure that there aren't any commits that have "Fix Issue 19105" in the commit meesage. The bot links to the issue if those magic words are present.

@John-Colvin
Copy link
Contributor

As a regression fix shouldn't this target stable?

@PetarKirov PetarKirov changed the base branch from master to stable December 1, 2019 20:14
@PetarKirov
Copy link
Member

Merging manually as the 'Windows_OMF x86' failure on Azure Pipelines is unrelated.

@PetarKirov PetarKirov merged commit d37b2af into dlang:stable Dec 1, 2019
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