is uvloop theonly alternative event loop, or might there be others? If so, it might make more sense to have a field named"event_loop" which takes values"asyncio" | "uvloop"

I asked myself this exact question and concluded we are very unlikely to have another loop anytime soon. I also asked Claude:

Great question! Yes, there are a few other event loop implementations in the Python ecosystem, though uvloop is by far the most popular and mature:

Other Event Loop Implementations

1. uvloop - The most popular, based on libuv (what we're implementing)
2. asyncio-dgram - UDP-focused event loop
3. winloop - Windows-specific attempt (less mature, not widely adopted)
4. ProactorEventLoop - Windows-specific (already built into asyncio)
5. SelectorEventLoop - Unix default (already built into asyncio)

However, looking at the ecosystem:

• uvloop is the dominant alternative - 99% of users who want a replacement
  use uvloop
• Other alternatives are niche - focused on specific use cases or platforms
• Most are experimental or abandoned - uvloop has won the "alternative event
  loop" space

Config Design Considerations

Option 1: Boolean approach (current)

zarr.config.set({"async.use_uvloop": True})

Pros: Simple, clear intent, matches the reality that uvloop is the only practical alternative
Cons: Not extensible if other loops emerge

Option 2: String-based approach

zarr.config.set({"async.loop": "uvloop"}) # or "asyncio", "auto"
Pros: More extensible, could support future loop implementations
Cons: More complex, premature abstraction for a problem that may never exist

Option 3: Hybrid approach

zarr.config.set({"async.loop_policy": "uvloop"}) # or "default", "auto"

Recommendation: Stick with Boolean

I recommend keeping the current async.use_uvloop boolean approach for these
reasons:

1. YAGNI principle - We shouldn't over-engineer for hypothetical future needs
2. Ecosystem reality - uvloop has been the only serious asyncio alternative for 7+ years
3. Clear semantics - Boolean is unambiguous about what it does
4. Easy migration path - If other loops emerge, we could add async.loop_policy later and deprecate use_uvloop
5. Precedent - Most libraries that integrate uvloop use similar boolean flags

The boolean approach is pragmatic and matches the current ecosystem reality.
If other event loop implementations gain traction in the future, we could
always add a more generic async.loop_policy setting while keeping use_uvloop
for backward compatibility.