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

Namespace Resolution #62

Open
AFg6K7h4fhy2 opened this issue Feb 6, 2025 · 0 comments
Open

Namespace Resolution #62

AFg6K7h4fhy2 opened this issue Feb 6, 2025 · 0 comments
Assignees
@AFg6K7h4fhy2

Comments

@AFg6K7h4fhy2
Copy link
Collaborator

As per DHM in #18 (see original comment here):

Still not convinced we should have such a large top-level namespace, but that's not for this PR

As such, this issue exists to resolve decisions pertaining to the namespace of this package. This process might include generating inclusion heuristics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AFg6K7h4fhy2 AFg6K7h4fhy2

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AFg6K7h4fhy2