-
-
Notifications
You must be signed in to change notification settings - Fork 706
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
Conversation
|
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 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
Testing this PR locallyIf 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" |
|
cc @RazvanN7 |
|
If I understand correctly, by reverting bug 20054 should also be fixed. Can you add a test for it in a separate commit? |
|
Done. However, this PR does not fix issue 19105. Is there some way I can tell the bot this? |
|
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. |
|
As a regression fix shouldn't this target stable? |
…ymbolsByUDA" This reverts commit 86733d5.
564772a to
a00f8c3
Compare
a00f8c3 to
2a2018c
Compare
|
Merging manually as the 'Windows_OMF x86' failure on Azure Pipelines is unrelated. |
…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.