-
Notifications
You must be signed in to change notification settings - Fork 9
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
Root Namespace #128
Comments
I don't care, that's just deciding on whether the paint of the shed needs to be a bit lighter or not... |
I really don't think the current two-level namespace makes a lot of sense. I think async-interop should use a single-level namespace to group its standards, and I think it'd be fine if that was Async or AsyncInterop, although the latter would better reflect the name of the organisation. |
At least https://github.com/jderusse/async uses |
https://bitbucket.org/mkjpryor/async/wiki/Home is another package using |
If we plan to use async-interop as the Composer vendor name then I think it's least surprising to use AsyncInterop as the namespace root. |
I feel strongly about this strategy, this is the least confusing for users and both vendor namespace, composer namespace, and the Github vendor/org match 👍 . |
The only reason I can see to continue with |
http://www.php-fig.org/psr/psr-4/ says the root namespace is the "vendor namespace", we aren't the "interop" vendor, we're the "async" vendor I'd say, but I don't feel strongly about it.
The text was updated successfully, but these errors were encountered: