[erlang-questions] Futures/promises and ability to "call" abstract modules
Joseph Wayne Norton
Tue Nov 20 16:32:41 CET 2012
Please see this repository if you are not already aware of it.
On Nov 21, 2012, at 12:20 AM, Gleb Peregud <> wrote:
> Since the resource associated with the process is always stored in
> heap of the process, the resource will not get garbage collected until
> no heap references it. This way we tie together process and resource
> lifetime. And since NIF resources can have a destructor in C which is
> called upon resource is garbage collected, we can make use of it to
> inform gcproc to terminate.
More information about the erlang-questions