basic data types
Mon, Mar 18
Still broken with that patchset.
Sun, Mar 17
Thu, Mar 14
Oh, that's interesting. I had an issue on my filesystem yesterday which resulted in a stat failing all the time which would lead to an Efl.Io.Model to always be in error. The patch D8336 is solving the error path and might actually solve also this problem too. Would be interesting to see if that does the case.
@cedric any other ideas?
Fri, Mar 8
Thu, Feb 28
Wed, Feb 27
Feb 14 2019
Feb 13 2019
Feb 11 2019
Feb 10 2019
Feb 9 2019
Feb 8 2019
Nice, will work at the weekend on that :)
@lauromoura I read out of your reply that you also want to see this feature going ?
- efl_class_functions_set class_ops should go away
- Every class API generated by Eolian will not have the first API
- Every implementation API will loose the first and second parameter.
Sure sure, I was asking "API-wise", that is, the only change that affects the API :)
No, we should also not allow this in eo at all. And change Eolians generation.
Given the headaches that mixins have given us, I'd say we avoid exotic features, yes.
API-wise, it's just a matter of Eolian erroring out when it finds a @class method inside an implements section, right?
@lauromoura How is that handled in c# ?
Feb 7 2019
Feb 6 2019
Feb 5 2019
After spending most of the day on this:
Here's a new one, I got a crash today:
I will try to handle it :)
Feb 4 2019
For documentation purposes, this is the deadlock backtrace:
If you move another test which uses SIMPLE_CLASS after that one and run synchronously then somehow it fucks up eo internals
I will be able to spend some time on this Wednesday morning if you want.
This is not entirly true, elm.hover inherits from efl.ui.focus.manager, and the efl_data_scope_get was on manager_calc
Can you elaborate on this ? This works here without a single issue.
While working on cleaning up the child model lifecycle of Efl.Io.Model for task T7528 I have found a few possible error that could explain the problem reported here. Could you check with that patch set if that solve the problem?
Something related to this is causing a deadlock in the unit test which occurs >50% of the time for me. This needs to be looked at urgently to verify that there isn't something wrong with model usage/implementation.