Question about threads

[Provalities]

@Mystifine

Do events / listeners automatically create new threads?

Yes, a listener does get called in a new thread, the above post is incorrect.

@LostPast

and are not actual new threads.

They are actual threads. Parallelism is not the same as concurrency. They are not “threads”.

@Mystifine

I have a lot of modules and normally within the function I’d use a spawn to make a new thread when there is a noticeable loop that will yield the rest of the script.

Module return values get cached for the computer requiring them, so the second require of the same module will return the same value as was returned by the first require. Clients have separate caches.

Never, under any circumstance, use the spawn function, use coroutines instead. This is because spawn will delay execution of the code for at least 1/30th of a second (because Roblox’s task scheduler runs 30 times a second, think of it as an additional unnecessary wait()), and they are unreliable (also avoid the delay function, wait function, and Debris service for similar reasons).

Horror stories about spawn if you don’t believe me:

Coroutines V.S. Spawn()... Which one should I use?

The title says it all… Basically I want to know in what scenarios I should use: spawn(function() -- Script end) And what scenarios I should use: local thing = coroutine.create(function() -- Script end) coroutine.resume(thing) So… When is it best to use spawn(function() and when it is best to use coroutines?