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 issue 21372: remove premature deprecation check. #11940
Fix issue 21372: remove premature deprecation check. #11940
Conversation
Thanks for your pull request and interest in making D better, @FeepingCreature! 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 run digger -- build "stable + dmd#11940" |
ad6e5c5
to
28686dc
Compare
28686dc
to
d2730e5
Compare
Looks like deprecation of variables broke. Okay, hm. Lemme look. |
d2730e5
to
2497022
Compare
Re-added the check only for variable declarations. |
I think the buildkite failure is spurious. Also, what's happening with the required hanging test passes? |
Buildkite has been fixed, try force pushing. |
Keep the check only for variable declarations.
2497022
to
d3a058a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's weird that VarDeclaration is done at this check and the rest later, and another red flag, but you got test coverage and improved the status quo, so 🤷
Slight note: You can use |
This pull request introduced a regression: |
This pull request fixed the regression: :-) |
Far as I can tell, without that check the deprecation just triggers later on.
Not sure if this is correct, let's see what the testsuite says.
edit: Oh yeah, I need to target stable cause it's a regression.