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
If esp:task_wdt_user_handle() is garbage collected, esp:task_wdt_reset_user/1 could not ever be called.
Should it be a resource that would delete itself when garbage collected?
This is debatable as having it as a resource implies that code that means to never call esp:task_wdt_reset_user/1, because it shall reboot or deep sleep before it is triggered, should keep a reference somehow.
See for example in la_machine:run/0, I keep a reference and unconfigure watchdog just before deep sleeping, but if we specified esp:task_wdt_user_handle() is not a resource, I could just let the binary be garbage collected.
The text was updated successfully, but these errors were encountered:
If
esp:task_wdt_user_handle()
is garbage collected,esp:task_wdt_reset_user/1
could not ever be called.Should it be a resource that would delete itself when garbage collected?
This is debatable as having it as a resource implies that code that means to never call
esp:task_wdt_reset_user/1
, because it shall reboot or deep sleep before it is triggered, should keep a reference somehow.See for example in la_machine:run/0, I keep a reference and unconfigure watchdog just before deep sleeping, but if we specified
esp:task_wdt_user_handle()
is not a resource, I could just let the binary be garbage collected.The text was updated successfully, but these errors were encountered: