How does it deal with pointers if everything is stack based? You can't really return a pointer to something on the stack because it could get overwritten between when you return it and when you access it.
func newPerson() *Person {
p := Person{Name: "Alice", Age: 30}
return &p
}
static main_Person* newPerson(void) {
main_Person p = (main_Person){.Name = so_str("Alice"), .Age = 30};
return &p;
}
So saying you get the "safety of Go" is a bit of a stretch.
Do an internet search for "go garbage collector benchmark" if you're curious what the grownups are talking about.
You can pass pointers to earlier frames in the stack, they're still active, but you can't return a pointer to an expired stack frame.
"Everything is stack-allocated by default; heap is opt-in through the standard library."
So it supports both stack and heap, and I guess static allocation too.