Thanks for reply, Ian To clear up, by safety I only mean presence of stack guards or, more generally, means of ensuring the program doesn't silently end up writing past the stack.
>From this I take my next step will be to make something between systemstack and asmcgocall so that I still run (subset of) Go while on systemstack but otherwise it would be as if it was a Cgo call, with minor difference that aligning stack and change of calling convention would happen at calls to C as opposed to at asmcgocall. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAEp866QQrqNUznSOFR4j_s6vW4X7ftEQVy48%3DH42UTBoe4DtXw%40mail.gmail.com.
