question: way not generator-rs Stack resizes automatically? about may

[Xudong-Huang]

The problem here is that the stack can't change it's address, resize or realloc the memory would change the stack address, and this would break every thing. Currently I don't know how to generate stack independent code in rust.

[zhuxiujia]

The problem here is that the stack can't change it's address, resize or realloc the memory would change the stack address, and this would break every thing. Currently I don't know how to generate stack independent code in rust.

Whether the required stack space size can be calculated at compile time？

[MSE99]

The problem here is that the stack can't change it's address, resize or realloc the memory would change the stack address, and this would break every thing. Currently I don't know how to generate stack independent code in rust.

I'm not really experienced in this topic, but i was wondering if it would it still break everything if for example coroutine A doesn't have any reference to any object allocated on the stack of coroutine B, in languages like erlang coroutines do not share memory by default and memory management (garbage collection, stack resizing) happens at the coroutine level rather than globally.

[zhuxiujia]

The problem here is that the stack can't change it's address, resize or realloc the memory would change the stack address, and this would break every thing. Currently I don't know how to generate stack independent code in rust.

I'm not really experienced in this topic, but i was wondering if it would it still break everything if for example coroutine A doesn't have any reference to any object allocated on the stack of coroutine B, in languages like erlang coroutines do not share memory by default and memory management (garbage collection, stack resizing) happens at the coroutine level rather than globally.
The expansion and contraction of coroutine memory are generally achieved by copying stack data onto a new stack,

The expansion and contraction of coroutine memory are generally achieved by copying stack data onto a new stack,

For example, the function of the coroutine internally initializes let arr=[0u8, 1u8, 2u8];

And the variable let b=&arr [1];

After the stack space shrinks, variable b becomes invalid, which will destroy everything