{"push_id":2760761527,"size":2,"distinct_size":2,"ref":"refs/heads/df_jitted_action","head":"10b40d1ece24a09843d7ed6ec927855a2b0da2de","before":"268a8902b79f5723841f3ee2f6508791ea0ad427","commits":[{"sha":"56f6427830eb2423420008b6e2e99117d6a3e04a","author":{"name":"Enrico Guiraud","email":"81a634b61c6957bc62fe9d7d41b6d1b9a925da25@cern.ch"},"message":"[DF] Add RJittedAction, a wrapper around jitted RAction's\n\nCurrently, jitted actions spawn into existence right before the event\nloop (at jitting time). This makes it impossible or unnecessarily complex to:\n1) let RResultPtrs own actions\n2) let actions own their previous node\n3) detect that an action has been booked before the event loop has run\nPoints 1 and 2 are required by ROOT-9416.\nPoint 3 is required by several graph-traversing features, e.g. ROOT-9458.\n\nThe solution is to align the jitted action logic with jitted filters and\ndefines, and use a placeholder RJittedAction object that sits into the\ncomputation graph and forwards all relevant calls to the concrete, jitted\naction which will be created at a later time.","distinct":true,"url":"https://api.github.com/repos/bluehood/root/commits/56f6427830eb2423420008b6e2e99117d6a3e04a"},{"sha":"10b40d1ece24a09843d7ed6ec927855a2b0da2de","author":{"name":"Enrico Guiraud","email":"81a634b61c6957bc62fe9d7d41b6d1b9a925da25@cern.ch"},"message":"[DF] Do not book Action in BuildAndBook, rename it to BuildAction\n\nWith the introduction of RJittedAction, jitted actions must not\nbe booked with the RLoopManager but instead they must be assigned\nto the corresponding RJittedAction. This commit prepares the ground\nfor this change in logic.","distinct":true,"url":"https://api.github.com/repos/bluehood/root/commits/10b40d1ece24a09843d7ed6ec927855a2b0da2de"}]}
{"actor":{"display_login":"bluehood"}}