questions about task_complete event uppon calling .list() or .size()

[2f5f3a1b567e0611949455401526cba2]

I got a co-routine that calls my_peripheral.list()
problem is, it seems to yield and my main event loop catches the event.

what is the intended way to handle this?

[fatboychummy]

Without knowing your actual code, there's no real advice I can give you about this other than just... Ignore the event?

Could you post your code?

[fatboychummy]

Oh, hold on, I missed the part about a coroutine. Coroutines should receive events based on three filters:

1. When you coroutine.resume the coroutine, it will return a value. This value is from os.pullEvent, being the event filter (e.g. "modem_message", etc). If this value is present, only resume the coroutine if the event matches that filter (or is "terminate").
2. Similarly, a coroutine.resumecall may return nothing. In this case, resume it for any received event.
3. As noted in 1, the event "terminate" bypasses all filters. Always send this event forward.

I recommend against working with raw coroutines though, especially if you aren't entirely sure how the event system works. Instead, use the parallel library, or if you wish to understand how it works, read its source.

[2f5f3a1b567e0611949455401526cba2]

here is a minimal (but verbose example i threw together to show the issue)

local function foo()
	local a = peripheral.wrap("left")
	print("-- Wrapped peripheral")
	a.list()
	print("-- Unreachable")
end

local co = coroutine.create(foo)
print("-- Created Coroutine")
coroutine.resume(co)
print("-- Coroutine yeilded")
local event  = { os.pullEvent() }
print("Got event ".. event[1])

Output:

-- Created Coroutine
-- Wrapped peripheral
-- Coroutine yeilded

[2f5f3a1b567e0611949455401526cba2]

I do understand that calling .list() yields,
but i tried to catch the task_complete event and call coroutine.resume()
but it did not work, so i reckon i just ask.

[fatboychummy]

Yes, just catching the event is not enough. You need to actually send the event back to the coroutine again, via coroutine.resume.

coroutine.resume(co, table.unpack(event)) -- passes the event to the coroutine

Again, highly recommend looking at how parallel does it, or just using parallel instead of running your own coroutine library. There's a lot of small issues that can occur when working manually with coroutines.

But I believe you may also be getting stuck on another hiccup of coroutines... Coroutines are not Threads. They do not run in the background. Lua is single-threaded, and so everything runs sequentially. Calling coroutine.resume actually switches to running your coroutine, then when it yields, it stops running.