You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent PR #305 unearthed some issues with how Defer and Go instructions are handled. These instructions are analogous to Call instructions, with some (important) differences in behavior:
Defer occurs when the defer keyword is used, which adds the call to a stack of calls to execute before the function returns.
Go starts the call in a new goroutine, meaning from that point on in the program, the instructions in the forked call could be interleaved with subsequent instructions in any order.
Currently, Defer instructions are not handled at all, while Go instructions are handled like regular calls.
The text was updated successfully, but these errors were encountered:
A recent PR #305 unearthed some issues with how
Defer
andGo
instructions are handled. These instructions are analogous toCall
instructions, with some (important) differences in behavior:Defer
occurs when thedefer
keyword is used, which adds the call to a stack of calls to execute before the function returns.Go
starts the call in a new goroutine, meaning from that point on in the program, the instructions in the forked call could be interleaved with subsequent instructions in any order.Currently,
Defer
instructions are not handled at all, whileGo
instructions are handled like regular calls.The text was updated successfully, but these errors were encountered: