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

use full type path in type resolution #173

Merged
merged 2 commits into from
Jan 3, 2020
Merged

use full type path in type resolution #173

merged 2 commits into from
Jan 3, 2020

Conversation

JeffBezanson
Copy link
Contributor

Currently a non-deterministic bug is possible if two different modules have a type with the same name. _resolve_type drops the first path component (the top-level module) and instead searches all modules in hash order. This fixes it by just using the whole path. I believe this was introduced by 9ef1e09. If this looks good I'll add a test.

@JeffBezanson
Copy link
Contributor Author

Hmm, this should probably also check that everything but the last component names a module.

@DilumAluthge
Copy link
Member

DilumAluthge commented Jan 2, 2020

This looks good to me. CI is passing.

It would be good to have a regression test.

@DilumAluthge
Copy link
Member

I've gone ahead and bumped the version number so that we can tag a new release as soon as we merge this PR.

@JeffBezanson
Copy link
Contributor Author

Ok should be set now.

@JeffBezanson JeffBezanson merged commit 83552a6 into master Jan 3, 2020
@JeffBezanson JeffBezanson deleted the jb/typepaths branch January 3, 2020 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants