The Phantom Derpstorm

This might be nice to do, albeit exceeedingly complicated and probably open up Yet Another Can Of Worms where I attempt to mix a thing that has had a notorious...

So, the reason you need `sol::thread` is because each of those coroutines needs its _own execution stack_. I call `sol::thread` by that name because that's how the Lua API and...

(To be clear, there is no `sol::execution_stack`. It doesn't exist; it's just a better name than `sol::thread`. Still, I need a good name for something like `coroutine_but_it_has_the_thread_too`...)

Current name idea so far is `sol::packed_coroutine`. This is also going to make me create a `sol3` header. where I create aliases under a `sol3::` namespace using _good_ names for...

Will be part of v4.

Ah, on the type. You can't do that right now because I didn't write a checker for this. This just grabs the table that repesents the usertype, not specifically _that_...

IF you're looking just for the value, that should work fine: https://godbolt.org/z/vMnobvEzo

You can use it for whatever you like still: https://godbolt.org/z/eqr68KP6q

(But I agree: I should just avoid registering it altogether.)

Thanks, I'll make sure to get it in the next sweep of changes.