English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Much initial research on automatic program repair has focused on experimentalresults to probe their potential to find patches and reduce development effort.Relatively less effort has been put into understanding the hows and whys ofsuch approaches. For example, a critical assumption of the GenProg technique isthat certain bugs can be fixed by copying and re-arranging existing code. Inother words, GenProg assumes that the fix ingredients already exist elsewherein the code. In this paper, we formalize these assumptions around the conceptof ''temporal redundancy''. A temporally redundant commit is only composed ofwhat has already existed in previous commits. Our experiments show that a largeproportion of commits that add existing code are temporally redundant. Thisvalidates the fundamental redundancy assumption of GenProg.

Do the Fix Ingredients Already Exist? An Empirical Inquiry into the Redundancy Assumptions of Program Repair Approaches