may

The caveat warns that accessing thread-local storage in coroutines can trigger undefined behavior, restricting common patterns and requiring careful code review to avoid issues.

Cannot call thread-blocking APIs without performance degradation, limiting interoperability with some libraries and systems that rely on synchronous operations.

Requires manual tuning of coroutine stack size to prevent overflow, adding complexity and potential for runtime errors if misconfigured, as noted in the documentation.

Compared to mainstream async runtimes like Tokio, May has a smaller community and ecosystem, which may affect long-term support, learning resources, and integration options.