forked from enlightenment/efl
5dbfb7961f
Efl.Future is an EO object which means even cancelling Efl.Future objects requires EO. So this should be done before shutting down EO, otherwise everything fails badly. I believe Efl.Future is going to disappear soon, but the problem will remain: if any promise/future uses EO or anything else outside of Eina (so, basically anything) then it needs to be canceled before shutting down the above layers. This is the same situation as with ecore events, for which we've introduced ecore_event_type_flush. Ping @cedric |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| Eo.h | ||
| efl_class.eo | ||
| efl_future.c | ||
| efl_future.h | ||
| efl_interface.eo | ||
| efl_object.eo | ||
| efl_object_override.eo | ||
| eina_types.eot | ||
| eo.c | ||
| eo_add_fallback.c | ||
| eo_add_fallback.h | ||
| eo_base_class.c | ||
| eo_class_class.c | ||
| eo_private.h | ||
| eo_ptr_indirection.c | ||
| eo_ptr_indirection.h | ||
| eo_ptr_indirection.x | ||