sleep 1#INF and spawn(1#INF) behavior

ID:2127146
 
Aug 5 2016, 10:24 am
BYOND Version:511.1350
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 52.0.2743.82
Applies to:Dream Daemon
Status: Open
Issue hasn't been assigned a status value.
/*

Q:  Does [sleep 1#INF] or [spawn(1#INF)] add anything to
    the scheduler?

A:  [sleep 1#INF] and [sleep(1#INF)] waits a single tick.

    [spawn(1#INF)] does seem to add to the scheduler,
        according to memory usage. I don't know if the code
        will ever execute or how long it would take.

*/

world
    fps = 60

var some_delay = 1#INF

mob
    var blah = 0

    verb/test_spawn()
        for(var/n in 1 to 1e3)
            spawn(some_delay)
                blah++

    verb/test_sleep()
        src << "Start time: [world.time]"
        sleep some_delay
        src << "End time: [world.time]"
        src << "Welcome past infinity."

    verb/check_blah()
        src << blah

As far as the bug report goes:

I feel like sleep 1#INF should halt the proc forever, never returning anything unless waitfor = FALSE;

and spawn(1#INF) just shouldn't add anything to the scheduler because it's a waste of memory.