[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Transaction Oriented GC algorithm in GoLang
- From: Jean-Luc Jumpertz <jean-luc@...>
- Date: Mon, 27 Jun 2016 09:06:10 +0200
> Le 25 juin 2016 à 17:47, Patrick Donnelly <firstname.lastname@example.org> a écrit :
> On Fri, Jun 24, 2016 at 6:45 PM, Javier Guerra Giraldez
> <email@example.com> wrote:
>> (i'm quite rusty with pcall(), but i think the intention is clear...)
>> of course, it would be a _lot_ better to avoid the function creation,
>> and instead have some language support to hook resource release
>> directly to scope exit:
>> local f = open(...)
>> onexit do f:close() end
>> .... do things with f ....
> For other readers, this has also been extensively discussed in this
> thread . In particular, see Roberto's proposal .
>  http://lua-users.org/lists/lua-l/2015-11/msg00152.html
>  http://lua-users.org/lists/lua-l/2015-11/msg00303.html
Although interesting, his is unrelated with the original subject of this discussion, that was about discussing possible ways of improving the current GC algorithm in Lua, by releasing values sooner when some locality conditions are satisfied (and not about releasing costly resources in a deterministic way).
Could we come back to the original subject? Thanks. :-)