Type checking error when using include_dir on windows #1077
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 path normalization issue causing type mismatches on Windows
The same type was being seen as mismatching because of different path
representations, even though the paths referred to the same file.
For example, "src\cc.d.tl:6" vs ".\src/cc.d.tl:6" would be treated
as different files, causing type comparison failures.
Changes:
it available to the core type checking system
This ensures all file paths are converted to a canonical form before
being used for type checking, file loading, and module resolution,
preventing the same file from being treated as different files when
referenced with different path representations.
Fixes the issue where global_env_def modules would cause type errors
on Windows due to inconsistent path normalization between backslashes
and forward slashes, relative and absolute paths.