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

Document Namespaces #924

Closed
Havvy opened this issue Jan 10, 2021 · 2 comments · Fixed by #937
Closed

Document Namespaces #924

Havvy opened this issue Jan 10, 2021 · 2 comments · Fixed by #937
Labels
A-resolve Name resolution, paths, namespaces, preludes, etc.

Comments

@Havvy
Copy link
Contributor

Havvy commented Jan 10, 2021

N.B.: This is a subpart of #568.

@ehuss: you state in #921 that they started an outline for this. Do you still have it, and if so, are you willing to show it?

If this is as daunting as you think it is, should we create a new branch to work on it?

@ehuss
Copy link
Contributor

ehuss commented Jan 10, 2021

I found a branch where I had started here: ehuss@bb2e84b

Since I think name resolution is a fairly meaty topic, I was thinking that it would be a good idea to separate it into separate files from the start with roughly that outline. One way to move forward on this is to just add resolve/name-resolution.md which gives a vague introduction, and resolve/namespaces.md, since I think the concept of namespaces is pretty straightforward and not too hard to document.

@ehuss ehuss added the A-resolve Name resolution, paths, namespaces, preludes, etc. label Jan 10, 2021
@Havvy
Copy link
Contributor Author

Havvy commented Jan 11, 2021

I'm of the opinion that anything is better than nothing and both of those pages look fine as is (modulo my wondering if "name resolution" is the best name). A starting point also makes it easier for others to contribute as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-resolve Name resolution, paths, namespaces, preludes, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants