Microsoft Technology Licensing, LLC

Peter Groenewegen

Mark Alistair Wilson-Thomas

Gustavo Araujo Soares

Arjun Radhakrishna

David Ellis Pugh

German David Obando Chacon

Piyush Arora

Sumit Gulwani

Andrew R Sterland

Vu Minh Le

Gregory Bernard Miskelly

Ashish Tiwari

Jonathan Preston Carter

Ivan Radicek

Titus Barik

Wode Ni

Ameya Sanjay Ketkar

Jonathan Keith Simmons

Aaron Chak Hei Yim

Edit automation functionality generalizes edits performed by a user in a document, locates similar text, and recommends or applies transforms while staying within a current workflow. Source code edits such as refactoring are automated. The functionality uses or provides anchor target lists, temporal edit patterns, edit graphs, automatable edit sequence libraries, and other data structures and computational techniques for identifying locations appropriate for particular edits, for getting transforms, for selecting optimal transforms, for leveraging transforms in an editing session or later, and for displaying transform recommendations and results. The edit automation functionality enhances automation subtool generation, discoverability, and flexibility, for refactoring, snippet insertion, quick actions in an integrated development environment, and other automatable edit sequences.

Edit automation using a temporal edit pattern

Some embodiments automatically assess source code merge conflict resolution candidates and then display a recommendation explaining strengths and weaknesses of each candidate. Thus informed, a developer can avoid adopting changes which produce merged code that does not build or does not pass tests, and avoid merged code that departs from a pattern followed in previous changes to a code base. Candidate conflict resolution assessments depend on objective criteria such as merged code buildability, operational accuracy, edit pattern consistency, or conflict resolution generator confidence. Candidates may be automatically ranked, prioritized, or rejected outright by an embodiment. Work item descriptions and candidate provenance may be displayed to aid developer selection of an optimal merge candidate.

Source code merge conflict resolution

Methods, systems, and computer program products for deploying a static code analyzer based on program synthesis from input-output examples. A computer system uses program synthesis on a set of input-output examples of source code edits to generate a rewrite rule that defines a transformation pattern. Based on a determined static code analyzer format, the computer system generates a static code analyzer from the rewrite rule. The static code analyzer includes a find portion that indicates a matching condition for identifying a portion of source code text, and a fix portion that indicates a textual replacement to apply to the portion of source code text matched by the find portion. The computer system deploys the static code analyzer to a development environment, including configuring the static code analyzer to be executable against a source code file within the development environment.

Deploying a static code analyzer based on program synthesis from input-output examples

Embodiments automate surfacing of underutilized development tool features, thereby enhancing the discoverability of subtools, commands, shortcuts, settings, visualizers, and other tool features. After spotting an inefficiency in the user's interaction with one or more tools, the feature surfacing functionality offers the user an interaction optimization suggestion. A mapping structure correlates detected interaction patterns with objectively better interaction optimizations. Several examples of mappings are discussed. The user can accept a suggestion, have the suggested optimization applied by an enhanced tool, and thereby reduce the number of user gestures utilized to accomplish a desired result, reduce the number of tools utilized, increase security, reduce risk of error, or get to the desired result faster, for example. Interaction optimizations also help the user stay focused, by reducing or avoiding departures from the user's current primary workflow. Other aspects of tool feature surfacing functionality are also described herein.

Surfacing underutilized tool features

Assisting automation of repeated edits of code by automated generation of rules that, when applied, perform code transformations. The transformations are synthesized while observing developers make repeated code edits, and automatically perform similar modifications as those observed. This synthesized transformation defines an initial state of code to which the transformation can be applied, and defines a modification from that initial state. A rule is then generated that includes a detector mechanism that, when selected, is configured to find locations in code that have the defined corresponding initial state of the corresponding transformation. Thus, the transformation may be applied to any code to which the rule is exposed.

Rules generation using learned repetitive code edits

Growing community of inventors

Vancouver, Canada

Peter Groenewegen