10:55:09beachhayley: Access to the thread object is just for additional return values yes?
10:56:20hayleyWe haven't come up with any other uses for it, but I suspect it would eventually also hold another "thread object" which would be used by other threads (say, in (bt:all-threads)), and thread-local allocator state.
10:57:20beachFair enough. However, for the current problem, I suggest we just generate a NAMED-CALL instruction with the additional return values.
10:57:53beachAccessing the thread object is going to be expensive, so an additional inexpensive named call is not going to make a difference.
10:58:26beachThe thread object is a standard object with an indirection, and the additional values might be in a vector with yet more indirection, etc.