make the stack size mishap note the pattern at which it happened (like the eval imit) #998
Description
Describe the feature
since Recursively Evaluated too deep has become <pattern>: Evaluated too many patterns, the same could be done with the stack size mishap to aid in debugging. for example, using Gemini Decomposition on a list whose size is greater than half of the stack limit would put you over, and show the mishap message Gemini Decomposition: exceeded the size limit of the stack.
Additional context
inevitably, this won't be a helpful message in every case; one I could think of would be if the offending data is the list returned from Thoth's Gambit. I can't think of any other pattern that returns a list possibly greater than the stack size limit, since it's unique in that the list construction step happens automatically with the size check happening after. another could be reading from a block/entity that has used HexDebug's Tachygraphy to avoid the limit. a special case mishap message might be useful for these, if Thoth's Gambit: Exceeded the size limit of the stack ends up not being too intuitive.