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

Fix Issue 20530 - is(<...> == module/package) does not work with stri… #10739

Merged
merged 1 commit into from
Jan 24, 2020

Conversation

BorisCarvajal
Copy link
Member

…ng mixins

I made the fix more general (changing getDsymbol) just to try, so far no problem in dmd test suite.

@dlang-bot
Copy link
Contributor

Thanks for your pull request and interest in making D better, @BorisCarvajal! 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
20530 normal is(<...> == module/package) does not work with string mixins

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 + dmd#10739"

@dlang-bot dlang-bot merged commit 890f7eb into dlang:stable Jan 24, 2020
@MoonlightSentinel
Copy link
Contributor

MoonlightSentinel commented Jan 24, 2020

[...] so far no problem in dmd test suite.

Because the test does only covers very few inputs of the trait. Some examples of the original test ( compilable/test16002.d) still don't work with this change:

alias a2 = mixin("imports.plainpackage");
alias b2 = mixin("imports.pkgmodule.plainmodule");

static assert(is(mixin("imports.plainpackage") == package));
static assert(is(mixin("a") == package));
static assert(is(a2 == package));
static assert(!is(mixin("imports.plainpackage.plainmodule") == package));
static assert(!is(mixin("b") == package));
static assert(!is(b2 == package));
// static assert(is(mixin("imports.pkgmodule") == package));  <= fails
static assert(!is(mixin("MyStruct") == package));

static assert(!is(mixin("imports.plainpackage") == module));
static assert(!is(mixin("a") == module));
static assert(is(mixin("imports.plainpackage.plainmodule") == module));
static assert(is(mixin("b") == module));

// static assert(is(mixin("imports.pkgmodule") == module)); // <= fails
static assert(!is(mixin("MyStruct") == module));

static assert(!is(mixin("imports.nonexistent") == package));
static assert(!is(mixin("imports.nonexistent") == module));

@BorisCarvajal
Copy link
Member Author

Thanks for the info, I'm going to check.
The module/package implementation have some weird spots.

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.

4 participants