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

Pattern namespacing #265

Open
morgante opened this issue Apr 22, 2024 · 0 comments
Open

Pattern namespacing #265

morgante opened this issue Apr 22, 2024 · 0 comments

Comments

@morgante
Copy link
Contributor

Right now it's hard to fork/copy patterns from the standard library because you end up with naming collisions between different patterns.

We should relax our requirements here and make module sharing easier.

  • Private patterns should only be "visible" inside the same pattern file, and should never collide with names outside the file.
  • Other patterns should allow renames in different repos. The name that takes precedence should be the one closest to the target repo. (ie. if I am applying code in repo A but import patterns from repo B any of my named patterns in repo A should override the same names in repo B).
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

1 participant