You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2018. It is now read-only.
My opinion is to keep things simple and only support manual memory management initially (i.e. malloc/free) and if a module doesn't do any malloc/free operations there would be no cost to the module.
Same philosophy here. MVP only support manual memory management. There is
another possible optimization, we can auto free allocated memory if it's
not referencing outside of a function and the instance is a local variable.
On Wed 12. Apr 2017 at 4:18 PM, Wink Saville ***@***.***> wrote:
What is the philosophy for memory management?
My opinion is to keep things simple and only support manual memory
management initially (i.e. malloc/free) and if a module doesn't do any
malloc/free operations there would be no cost to the module.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMGZud4HuiQlfOVYko0RyUp_iH3oNy2ks5rvN0sgaJpZM4MrbFx>
.
object = null
is standard way to signalize for GC to forcing delete object by reference in js.The text was updated successfully, but these errors were encountered: