Split C++11-specific tests in their own file#9185
Split C++11-specific tests in their own file#9185thewilsonator merged 3 commits intodlang:masterfrom
Conversation
|
Thanks for your pull request, @Geod24! Bugzilla referencesYour 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 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 "master + dmd#9185" |
|
Thanks! |
|
Sweet, it does not work (except on Linux and MacOS ofc). Windows: @ibuclaw do you want to take a look at it or shall I ? |
|
I have no care for the windows mangling (itanium is used for all platforms including windows my end). I have a FreeBSD VM around somewhere, however my initial assumption is that the version of gcc installed on the box is old (I think gcc 4.7 or older) See my comment on abi timeline of nullptr_t. |
|
You could try setting false if FreeBSD in the new target hook to verify. |
VC uses back references for std::nullptr_t, too, so adding this to VisualCPPHndler.visit(TypeNull) should help: |
764a28f to
295b5ed
Compare
When it comes to C++ interop, many bugs are mangling related. As we add more and more tests involving the STL, the linker errors become more advance and subtle, and getting those on a platform one does not have access to (e.g. FreeBSD) is usually hard to debug, as we deal with different compiler/stdlib versions.
7a59a88 to
9bba34e
Compare
Suggested by `@rainers`
|
This is all green. Good to go? |
|
Well the test is disabled on most platforms, but this is why you should not merge commented out tests, they rarely work. |
|
And that first commit should make it easier for Manu to do remote debugging. |
|
Auto-merge toggled on |
Follow up on the eager merge of #9138