This is a partial implementation, but shows how to use on the test. It is still specific to methods only on this diff. But I'll expand to other entities.
Tue, Oct 15
Sat, Oct 12
Add since documentation to Async methods
Sorry. Forgot to accept it first. But I've tested and "accepted" it.
Tue, Oct 1
Mon, Sep 30
Sep 9 2019
Sep 4 2019
Sep 3 2019
Still missing the check by C#
Aug 23 2019
Aug 21 2019
Aug 19 2019
I'd really like @segfaultxavi opinion about the idea.
arc patch didn't retrieve a different commit message
Aug 16 2019
The D9576 also fixes one problem with ASAN when building. For me when both patches are applied no issues appear in ASAN. Can you check that D9576 fixes the building ASAN issue? I"ll check the test one, I forgot to test it when fixing the normal build.
Aug 15 2019
Env class has an env property. It is multi-valued, so it is not generating a problem for C# yet. But it may in the future.
Aug 14 2019
The property could still be generated, but only with get;
Also, we can use property names in tuples, so users can set by property name instead of using ordering.
Aug 13 2019
Aug 11 2019
OK. This is what we needed to modify factories.
Aug 8 2019
I'll let other people chime in. If nobody else opposes, then IMO you can go ahead and reinclude it. If that happens, then we need a solution for T8118 first, IMO.
By size I mean typing more. I'm not against it per se, but for static use it doesn't look like a good tradeoff to me. This is going to uglify bindings and I don't really see much of a difference in change the name of the method or pass a different type. It actually creates one more point for error, where people can pass wrong classes, they can't when the class is embed in the function name.
About factories: what is the difference between:
Do we have a use case? Features are nice, but I think they must be justifiable.
Aug 7 2019
Aug 5 2019
Jul 31 2019
C++ patches are pushed
Jul 25 2019
Jul 23 2019
Well, a clang frontend plugin could guarantee that EFL_TRANSFER_OWNERSHIP is written in all EFL where it should.
Without typing checking, how useful it really is? Can't we make it type-checked? Even if by use of extension for a single compiler?
Jul 22 2019
Jul 17 2019
This task is related to https://phab.enlightenment.org/D9070
Apr 23 2019
We can avoid the performance problems by creating a boolean if someone is registered in the event. The event won't get called most of the time because most objects have a parent anyway and the event gets called just for objects with C# wrappers.
Apr 15 2019
So we looked into the problems of finalizers and dispose and we found out that using that is not possible. It is possible the GC collects members of a class that we decide later to ressucitate. That surely wouldn't work, because the members would not have the same state when the class is revived.
Apr 9 2019
Remove test that is not working
Apr 8 2019
Do not register Efl.Object again and again