It looks that semantic of lazy method is different than described in javadoc. Review current behaviour and change implementation or javadoc.
Anyway, it would be usefull to have this type of lazy scheduler, but I am afraid it would require some global state.
Probably we must track "the same action" in different way than by "action identity", because it is very fragile for lambda expressions.
It looks that semantic of `lazy` method is different than described in javadoc. Review current behaviour and change implementation or javadoc.
Anyway, it would be usefull to have this type of lazy scheduler, but I am afraid it would require some global state.
Probably we must track "the same action" in different way than by "action identity", because it is very fragile for lambda expressions.
Probably we should pass as an argument previously created "Cancelable" or null.
LazyCancelable should be used, to CAS operation, to cancel previous task without race conditions.
Probably we should pass as an argument previously created "Cancelable" or null.
LazyCancelable should be used, to CAS operation, to cancel previous task without race conditions.
It works, usage was completely surprising. But it works perfectly and it doesn't have any problems with identity, lambda etc.
It is just factory method, created object can be used to execute/cancel execution of code later.
It works, usage was completely surprising. But it works perfectly and it doesn't have any problems with identity, lambda etc.
It is just factory method, created object can be used to execute/cancel execution of code later.
It looks that semantic of
lazymethod is different than described in javadoc. Review current behaviour and change implementation or javadoc.Anyway, it would be usefull to have this type of lazy scheduler, but I am afraid it would require some global state.
Probably we must track "the same action" in different way than by "action identity", because it is very fragile for lambda expressions.
Probably we should pass as an argument previously created "Cancelable" or null.
LazyCancelable should be used, to CAS operation, to cancel previous task without race conditions.
To be specific: it looks that LazyCancelable is totally broken ;-)
It works, usage was completely surprising. But it works perfectly and it doesn't have any problems with identity, lambda etc.
It is just factory method, created object can be used to execute/cancel execution of code later.