native::start does not know the stack boundary

[alexcrichton]

Once libnative lands, the start function will have no knowledge of the stack boundaries on the main thread. This is far less than ideal because the main thread is no longer protected from stack overflow.

Crates which link to libnative and don't override #[start] will have their main function executed in a separate thread to get around this, but crates using libnative should at least be made aware of this (or we should figure out the current thread's stack size).

[alexcrichton]

Closing in favor of #11359, most of the issue was taken care of in #11360