+1. There's a reason cgo sets up another stack; calling into Rust instead of C doesn't change that. What are the consequences if you blow the stack in Go [edit

+1. There's a reason cgo sets up another stack; calling into Rust instead of C doesn't change that. What are the consequences if you blow the stack in Go [edit: to clarify, I mean if your code in another language that doesn't understand Go's stack copying calling convention blows Go's stack]? Is there a guard page (so SIGSEGV) or does it just corrupt memory?