Skip to content

Comments

Delete hack to always do codegen for templates if -debug is used#10968

Merged
dlang-bot merged 2 commits intodlang:masterfrom
atilaneves:wip-test-template-debug
Apr 11, 2020
Merged

Delete hack to always do codegen for templates if -debug is used#10968
dlang-bot merged 2 commits intodlang:masterfrom
atilaneves:wip-test-template-debug

Conversation

@atilaneves
Copy link
Contributor

@atilaneves atilaneves commented Mar 27, 2020

This PR deletes code that special cases -debug/-unittest when considering whether or not to do codegen for templates in non-root modules. It also deletes a dmd test that's no longer necessary due to Phobos having been updated in the meanwhile (there used to be a debug block in std.range that caused linker errors due to template instantiation with -debug).

Relevant issues and PR:

https://issues.dlang.org/show_bug.cgi?id=12661
https://issues.dlang.org/show_bug.cgi?id=15230
#4944

@atilaneves atilaneves force-pushed the wip-test-template-debug branch from b1496a9 to 12d612b Compare April 1, 2020 17:09
@atilaneves
Copy link
Contributor Author

Blocked by dlang/phobos#7439

@atilaneves atilaneves force-pushed the wip-test-template-debug branch from 12d612b to 2486aa6 Compare April 10, 2020 12:25
@atilaneves atilaneves marked this pull request as ready for review April 10, 2020 12:26
@atilaneves atilaneves changed the title [WIP] Delete hack to always do codegen for templates if -debug is used Delete hack to always do codegen for templates if -debug is used Apr 10, 2020
@dlang-bot
Copy link
Contributor

Thanks for your pull request and interest in making D better, @atilaneves! 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

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

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#10968"

@dlang-bot dlang-bot merged commit f343ce1 into dlang:master Apr 11, 2020
@atilaneves atilaneves deleted the wip-test-template-debug branch April 15, 2020 15:01
@UplinkCoder
Copy link
Member

This caused a ICE to appear in our code.

@UplinkCoder
Copy link
Member

also why are you deleting this tests ... they should still pass after this PR?

@wilzbach
Copy link
Contributor

This caused a ICE to appear in our code.

Is it possible to isolate the code to a reduced example?

@UplinkCoder
Copy link
Member

UplinkCoder commented May 29, 2020

Is it possible to isolate the code to a reduced example?

possible. yes.

My comment is less about a particular example, and more about doing invasive changes in poorly understood systems ...
I can reduce it for completeness sake.

@atilaneves
Copy link
Contributor Author

also why are you deleting this tests ... they should still pass after this PR?

They weren't very good tests and not relevant anymore. They were testing that there were no linker failures with Phobos code that doesn't even exist anymore.

@WalterBright
Copy link
Member

This has caused a regression https://issues.dlang.org/show_bug.cgi?id=15985

@ibuclaw
Copy link
Member

ibuclaw commented Jan 29, 2023

This has caused a regression https://issues.dlang.org/show_bug.cgi?id=15985

Issue was created in 2016, this PR was created in 2020. Unless I've forgotten how time works, no it didn't. :-)

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.

7 participants