Skip to content
New issue

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

Question about #REQUIRE #261

Open
fblanqui opened this issue Jan 5, 2022 · 3 comments
Open

Question about #REQUIRE #261

fblanqui opened this issue Jan 5, 2022 · 3 comments

Comments

@fblanqui
Copy link
Member

fblanqui commented Jan 5, 2022

#REQUIRE does not seem necessary and can be ignored. What is it for?

@amelieled
Copy link

Same question for #NAME.

@francoisthire
Copy link
Collaborator

#NAME was deprecated, the time the libraries could be adapted.

#REQUIRE is not necessary but I know some situations where it is necessary.

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.

@francoisthire
Copy link
Collaborator

@fblanqui can this issue be closed? What do you expect to solve it otherwise?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants