We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently when we see a module, we decide that the given file depends on all the previous files and all the files above it depend on it:
fsharp/tests/ParallelTypeCheckingTests/Code/DependencyResolution.fs
Lines 161 to 163 in ae0e40b
This is a safety we need without fully understanding the behaviour and implementing it.
This ticket is to avoid this defensive mechanism.
Also: module abbreviations in signature files are currently not supported, we should fix it:
fsharp/tests/ParallelTypeCheckingTests/Code/ASTVisit.fs
Line 1147 in ae0e40b
The text was updated successfully, but these errors were encountered:
This is being handled in #24
Sorry, something went wrong.
No branches or pull requests
Currently when we see a module, we decide that the given file depends on all the previous files and all the files above it depend on it:
fsharp/tests/ParallelTypeCheckingTests/Code/DependencyResolution.fs
Lines 161 to 163 in ae0e40b
This is a safety we need without fully understanding the behaviour and implementing it.
This ticket is to avoid this defensive mechanism.
Also: module abbreviations in signature files are currently not supported, we should fix it:
fsharp/tests/ParallelTypeCheckingTests/Code/ASTVisit.fs
Line 1147 in ae0e40b
The text was updated successfully, but these errors were encountered: