search

async-interop / event-loop

An event loop interface for interoperability in PHP.
MIT License
169 stars 9 forks source link

Root Namespace #128

Closed kelunik closed 7 years ago

kelunik commented 7 years ago

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.

bwoebi commented 7 years ago

I don't care, that's just deciding on whether the paint of the shed needs to be a bit lighter or not...

joshdifabio commented 7 years ago

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.

kelunik commented 7 years ago

At least https://github.com/jderusse/async uses Async currently.

kelunik commented 7 years ago

https://bitbucket.org/mkjpryor/async/wiki/Home is another package using Async, found via http://packanalyst.com/.

joshdifabio commented 7 years ago

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.

WyriHaximus commented 7 years ago

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 :+1: .

trowski commented 7 years ago

The only reason I can see to continue with Interop\Async is that container-interop uses Interop\Container. Aside from that, AsyncInterop would be the obvious choice.