I’m curious what happens if you use await for a signal, but the signal is never received? Does this cause some kind of hangup?

For example if I have a function structured like so:

func foo():
    do something
    await signal.finished
    do something else

And the “finished” signal never comes, does the await call just hang indefinitely?

  • Jozzo@lemmy.world
    14·
    10 months ago

    Just tried this out in one of my projects, here’s what happened:

    • do something works without a problem.
    • do something else never goes off.
    • the rest of the game keeps running as normal. You can even call foo() again any number of times and do something will still go off.

    Having it waiting in the background didn’t seem to have much of a performance impact. I started 5000+ of them and foo() only took up ~0.6% frametime with the rest of my game running alongside it.

    • plixel@programming.devOP
      4·
      10 months ago

      Thanks so much for testing that out! That’s very informative and even more thorough than what I was looking for! I wasn’t at my computer when I posted this so I couldn’t test it myself.

      I ended up connecting the signal to a secondary function to run on finished to avoid any potential memory errors, but it’s super helpful to know that the performance impact is minimal.