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
#REQUIRE does not seem necessary and can be ignored. What is it for?
The text was updated successfully, but these errors were encountered:
Same question for #NAME.
Sorry, something went wrong.
#NAME was deprecated, the time the libraries could be adapted.
#NAME
#REQUIRE is not necessary but I know some situations where it is necessary.
#REQUIRE
Assume I have three modules (dk files):
The first one (X.dk)
def A : Type. B : Type. def a : A. b : B.
The second one (Y.dk)
[] X.A --> X.B.
The third one (Z.dk)
[] X.a --> X.b.
The third one is not well-typed. However, if I add #REQUIRE Y. in Z.dk it becomes well-typed.
#REQUIRE Y.
Z.dk
@fblanqui can this issue be closed? What do you expect to solve it otherwise?
No branches or pull requests
#REQUIRE does not seem necessary and can be ignored. What is it for?
The text was updated successfully, but these errors were encountered: