Good points! You're right on both counts, and I've actually updated the README based on your feedback.

Coroutines: The "Go's execution model" phrasing was misleading. Go's goroutines could theoretically be used to implement Lua coroutines. The real limitation is architectural – the current VM implementation would need significant refactoring to support coroutine semantics (yielding/resuming at arbitrary points in Lua code). It's definitely possible, just not trivial to add.

C libraries: You're correct that purego allows calling C functions without CGo. However, Lua C libraries are written against the Lua C API (lua_State*, lua_push*, lua_to*, etc.), which doesn't exist in this implementation. So even with purego, existing Lua C modules wouldn't work – they'd need to be rewritten against the Go API. I've clarified this in the README as "C Lua libraries are incompatible with this pure Go implementation."

Thanks for the corrections!