To be fair, the prerequisites of the language specification aren't nearly as wide as the prerequisites of the entire standard library in general. Implementations like GopherJS are (I think) spec-compliant but don't implement some parts of the standard library due to the constraints of the environment. I'm not necessarily vouching for a GrowCurrentStackTo API, though.
On Wed, Jul 26, 2017 at 9:24 AM T L <[email protected]> wrote: > > > On Wednesday, July 26, 2017 at 10:37:44 AM UTC-4, Jan Mercl wrote: > >> On Wed, Jul 26, 2017 at 4:26 PM T L <[email protected]> wrote: >> >> > BTW, I think we do need a GrowCurrentStackTo API, to avoid predicted >> several stack copies in stack growing. >> >> The specification does not requires Go implementations to have any stack >> at all. >> > > we can just add it in the debug package, just like > runtime/debug.SetMaxStack. > > >> >> -- >> >> -j >> > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
