Regarding your 'onleave' idea; go has a similar construct called defer [1], it is exactly what you are talking about and (imo) is a really elegant way of dealin

Regarding your 'onleave' idea; go has a similar construct called defer [1], it is exactly what you are talking about and (imo) is a really elegant way of dealing with cleanup. [1]http://golang.org/doc/effective_go.html#defer http://golang.org/doc/effective_go.html#defer