I think it will least surprise users if "stack" means the stack actually
available to the thread, not including implementation details such as TLS,
so they can work with tools that determine the amount of stack space used
by individual functions to work out how large a stack may be needed.
I think it will least surprise users if "stack" means the stack actually
available to the thread, not including implementation details such as TLS,
so they can work with tools that determine the amount of stack space used
by individual functions to work out how large a stack may be needed.