acarioni

Thanks for the explanation, Aurel. IMO the compiler should at least emit a warning when there is a comparison of two values of an enum type comprising constructors with arguments,...

I found that adding the nullSafety annotation before "this" makes disappear the error. ``` a1 = new A1(@:nullSafety(Off) this) ```

But `Executor.create` prints only some logging messages. In general term, I think that if a class A depends on a class B, haxe should emit code where the static fields...

Sure. `Executor.create` calls the constructor of `hx.concurrent.ServiceBase`, that in python is implemented in the following way ``` def __init__(self): self._stateLock = hx_concurrent_lock_RLock() self.state = hx_concurrent_ServiceState.STOPPED self.id = hx_concurrent_ServiceBase._ids.incrementAndGet() haxe_Log.trace((("[" +...

Yes! It triggers the same warnings and errors. The error is ``` Type foo.Child$Closure_new_0 is defined multiple times: /Users/foobar/temp/bin/android/Parent.jar:foo/Child$Closure_new_0.class, /Users/foobar/temp/bin/android/Parent.jar:foo/Child$Closure_new_0.class Duplicate class foo.Child$Closure_new_0 found in modules Parent (Parent.jar) and Parent...

Thank you. I'll try and I'll let you know.

Hello Simon, The patch works very well and fixes the error. However the warnings are still there.

The error and the previous warnings have disappeared, but now there are two new warnings. Apart from them, the generated output works fine in Android. Invalid stack map table at...

My main objection is that in general a user doesn’t know (and should not know) on which thread the timer is going to be executed (and btw the documentation of...

As another example of why the actual implementation of Timer is a source of bugs in multithreaded applications, consider the following scenario that I’ve discovered a few days ago while...