Program synthesis

From formulasearchengine
Jump to navigation Jump to search

{{ safesubst:#invoke:Unsubst||$N=Refimprove |date=__DATE__ |$B= {{#invoke:Message box|ambox}} }} Template:Data transformation Program synthesis is a special form of automatic programming that is most often paired with a technique for formal verification. The goal is to construct automatically a program that provably satisfies a given high-level specification. In contrast to other automatic programming techniques, the specifications are usually non-algorithmic statements of an appropriate logical calculus.[1]


The idea originated in the 60s {{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{#invoke:Category handler|main}}{{#invoke:Category handler|main}}[citation needed] }} with the aim of using techniques from artificial intelligence to build an automatic programmer{{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{#invoke:Category handler|main}}{{#invoke:Category handler|main}}[citation needed] }}, exploiting deep connections between mathematics and the theory of programming. Lack of early success meant that the mathematical approach soon fell out of favour, along with enthusiasm for AI, in general. Although some researchers Template:Who still work on formal approaches, more success has been obtained by combining pure deductive techniques with powerful heuristics, and limiting their application to specific domains.{{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{#invoke:Category handler|main}}{{#invoke:Category handler|main}}[citation needed] }}

Problems and Limitations

Some feelTemplate:Who that the concept of automated program generation often results in poor "factoring" of information.{{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{#invoke:Category handler|main}}{{#invoke:Category handler|main}}[citation needed] }} Known redundancy should be Template:Why? factored out, not introduced, it is said Template:Who{{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{#invoke:Category handler|main}}{{#invoke:Category handler|main}}[citation needed] }}. However, sometimesTemplate:Vague specific programming languages are limited such that one has to introduce repetition of a concept or pattern in order to keep using the same language.{{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{#invoke:Category handler|main}}{{#invoke:Category handler|main}}[citation needed] }} Here is a simplified illustration of factoring:

Poor Factoring: x = a + a + a + a + a

Good Factoring: x = a × 5

Program generation tends to focus on automating the repetition seen in the first example, when a better approach is perhapsTemplate:Vague to find a higher-order abstraction, which is multiplication in this case. Other examples include putting parameters into a file or database instead of inside application code.

The Framework of Manna and Waldinger

The framework of Manna and Waldinger [2] starts from a user-given first-order specification formula. For that formula, a proof is constructed, thereby also synthesizing a functional program from unifying substitutions. Proof rules include non-clausal resolution, logical transformations, splitting of conjunctive assertions and of disjunctive goals, and structural induction. Murray has shown these rules to be complete for first-order logic.[3] In 1986, Manna and Waldinger added generalized E-resolution and paramodulation rules to handle also equality;[4] later, these rules turned out to be incomplete (but nevertheless sound).[5]

The framework has been designed to enhance human readability of intermediate formulas: contrary to classical resolution, it does not require clausal normal form, but allows one to reason with formulas of arbitrary structure and containing any junctors. Programs obtained by this approach are guaranteed to satisfy the specification formula started from; in this sense the are correct by construction. Only a minimalistic, yet turing-complete functional programming language, consisting of conditional, recursion, and arithmetic and other operators is supported.

As a toy example, a functional program to compute the maximum of two numbers and can be derived as follows.

Example synthesis of maximum function
Nr Assertions Goals Program Origin
1 Axiom
2 Axiom
3 Axiom
10 M Specification
11 M Distr(10)
12 M Split(11)
13 M Split(11)
14 x Resolve(12,1)
15 x Resolve(14,2)
16 x Resolve(15,3)
17 y Resolve(13,1)
18 y Resolve(17,2)
19 x<y ? y : x Resolve(18,16)

Starting from the requirement description "The maximum is larger than any given number, and is one of the given numbers", the first-order formula is obtained as its formal translation. This formula is to be proved. By reverse Skolemization,[6] the specification in line 10 is obtained, an upper- and lower-case letter denoting a variable and a Skolem constant, respectively. After applying the distributive law in line 11, the proof goal is a disjunction, and hence can be split into two cases, viz. lines 12 and 13. Turning to the first case, resolving line 12 with the axiom in line 1 leads to instanciation of the program variable in line 14. Intuitively, the last conjunct of line 12 prescribes the value that must take in this case. Formally, the non-clausal resolution rule shown in line 57 below is applied to lines 12 and 1, with

yielding , which simplifies to . In a similar way, line 14 yields line 15 and then line 16 by resolution. Also, the second case, in line 13, is handled similarly. In a last step, both cases (i.e. lines 16 and 18) are joined, using the resolution rule from line 58; to make that rule applicable, the preparatory step 15→16 was needed. Since both line 16 and 18 comes with a program term, a conditional expression results in the program column. Since the goal formula has been derived, the proof is done, and the program column of the "" line contains the program.

Non-clausal resolution rules (unifying substitutions not shown)
Nr Assertions Goals Program Origin
53 s
54 t
55 Resolve(51,52)
56 s Resolve(52,53)
57 s Resolve(53,52)
58 p ? s : t Resolve(53,54)

See also


  1. {{#invoke:citation/CS1|citation |CitationClass=book }}
  2. {{#invoke:Citation/CS1|citation |CitationClass=journal }} A preprint appearead in Dec 1978 as SRI Technical Note 177
  3. Manna, Waldinger (1980), p.103, referring to: Template:Cite techreport
  4. {{#invoke:Citation/CS1|citation |CitationClass=journal }}
  5. {{#invoke:citation/CS1|citation |CitationClass=book }}
  6. While ordinary Skolemization preserves satisfiability, reverse Skolemization, i.e. replacing universally quantified variables by functions, preserves validity.
  • {{#invoke:Citation/CS1|citation

|CitationClass=journal }}

  • {{#invoke:citation/CS1|citation

|CitationClass=book }}