Thanks for the link. I don't think it's too relevant: this is basically an implementation detail for how one chooses to attach the data to a closure pointer. We've opted to make closure "pointers" two words, one for the environment and one for the code pointer. Go seems to be moving to a one word representation where you point to the environment and the environment points to the code. This has some advantages (pointers are smaller) but also some disadvantages (you can't convert a top-level function into a closure without allocation).
Niko On Wed, Oct 02, 2013 at 02:51:17AM -0400, Corey Richardson wrote: > Saw this on HN: > https://docs.google.com/a/octayn.net/document/d/1bMwCey-gmqZVTpRax-ESeVuZGmjwbocYs1iHplK-cjo/pub > > I haven't been following the recent closure discussions much, but what > Go is doing might be relevant? > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
