“At any given time, a developer will approach a code base and make changes with one or more intents in mind”, the members of the Google Brain team wrote in a paper, “It is … an interesting research challenge, because edit patterns cannot be understood only in terms of the content of the edits (what was inserted or deleted) or the result of the edit (the state of the code after applying the edit). An edit needs to be understood in terms of the relationship of the change to the state where it was made, and accurately modeling a sequence of edits requires learning a representation of the past edits that allows the model to generalize the pattern and predict future edits.”

Full paper on Arxiv.org

Leave a comment

Your email address will not be published. Required fields are marked *