Fix implicit usage paths#977
Merged
Merged
Conversation
- When hashing, only the last path element needs to be hashed (module names are unambiguous, but the same module can be accessed through multiple dependency paths - Anyway, for type names, we strip the path in the same way: that seems cleaner e.g. in error messages. But the 1st point is enough to fix the bug
vincent-botbol
force-pushed
the
fix-implicit-usage-paths
branch
from
e2a9370 to
965c511
Compare
This was referenced Mar 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 implicitly open types path resolution & hash discrepancy
Sister PR: CatalaLang/catala-examples#40