Conference paper Open Access

Programming with a Read-Eval-Synth Loop

Peleg, Hila; Gabay, Roi; Itzhaky, Shachar; Yahav, Eran

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="DOI">10.5281/zenodo.4038334</identifier>
      <creatorName>Peleg, Hila</creatorName>
      <affiliation>University of California, San Diego</affiliation>
      <creatorName>Gabay, Roi</creatorName>
      <creatorName>Itzhaky, Shachar</creatorName>
      <creatorName>Yahav, Eran</creatorName>
      <affiliation>Codota and Technion</affiliation>
    <title>Programming with a Read-Eval-Synth Loop</title>
    <date dateType="Issued">2020-09-19</date>
  <resourceType resourceTypeGeneral="Text">Conference paper</resourceType>
    <alternateIdentifier alternateIdentifierType="url"></alternateIdentifier>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsVersionOf">10.5281/zenodo.4038333</relatedIdentifier>
    <rights rightsURI="">Creative Commons Attribution 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&lt;p&gt;A frequent programming pattern for small tasks, especially expressions, is to repeatedly evaluate the program on an input as its editing progresses. The Read-Eval-Print Loop (REPL) interaction model has been a successful model for this programming pattern. We present the new notion of Read-Eval-Synth Loop (RESL) that extends REPL by providing in-place synthesis on parts of the expression marked by the user. RESL eases programming by synthesizing parts of a required solution. The underlying synthesizer relies on a partial solution from the programmer and a few examples.&lt;/p&gt;

&lt;p&gt;RESL hinges on bottom-up synthesis with general predicates and sketching, generalizing programming by example. To make RESL practical, we present a formal framework that extends observational equivalence to non-example specifications.&lt;/p&gt;

&lt;p&gt;We show the value of RESL by conducting a controlled within-subjects user-study on 19 programmers from 8 companies, where programmers are asked to solve a small but challenging set of competitive programming problems. We find that programmers using RESL solve these problems with far less need to edit the code themselves and by browsing documentation far less. In addition, they are less likely to leave a task unfinished and more likely to be correct.&lt;/p&gt;

All versions This version
Views 7676
Downloads 77
Data volume 17.0 GB17.0 GB
Unique views 7474
Unique downloads 77


Cite as