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.

Sign up for GitHub

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

Jump to bottom

Naming in range.ml #187

Open
mikeshulman opened this issue Nov 2, 2024 · 1 comment
Open

Naming in range.ml #187

mikeshulman opened this issue Nov 2, 2024 · 1 comment
Labels
design is needed documentation Improvements or additions to documentation

Comments

@mikeshulman
Copy link
Collaborator

I am never sure whether to open Asai.Range or not. On one hand, it contains functions and types that it would be convenient to be able to refer to unqualified, like located and locate. But on the other hand, it contains the type t which is clearly intended to be used qualified, and I'd rather not pollute my root namespace with a type called t.
@favonia favonia added documentation Improvements or additions to documentation design is needed labels Nov 2, 2024
@favonia
Copy link
Contributor

favonia commented Nov 2, 2024 •
edited
Loading

I think it's good to think about this issue when (re)designing locations and diagnostics (#184 and #169).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design is needed documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mikeshulman @favonia