DynCallable exhibits use-after-move / double-invoke undefined behavior
DynCallable exhibits use-after-move / double-invoke undefined behavior: a task in LegoFlow-SWE (Harbor dataset). When using the type-erased callable wrapper DynCallable , operations that are performed after the underlying callable’s state has been invalidated lead to undefined behavior. The…
The task
When using the type-erased callable wrapper `DynCallable`, operations that are performed after the underlying callable’s state has been invalidated lead to undefined behavior. The problem appears in two scenarios:
Part of Lego-X/LegoFlow-SWE.