Fix loader with paths to module types #128
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #121 (with a simplified minimal reproduction in the test).
Consider the following signature items:
Here, the module type of
A
is the module type ofA.B.Y
(which is a path to a module). This is represented inTypes
asMty_alias path
.The module type of
B
isA.B.Y
(which is a path to a module type). This is represented inTypes
asMty_ident path
.Before this PR, the two cases were treated equally, as if they were path to modules.
We now distinguish the two cases.
(This PR does not address the fact that we do not expand module types during loading! But we are not diffing them anyway as of today.)