Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/working/resolver_design.md

    rac43954 rbbd44c5  
    13821382hypothesis needs to be empirically validated.
    13831383
     1384Another approach would be to abandon expression-tree ordering for
     1385subexpression matching, and order by "most constrained symbol"; symbols would 
     1386be more constrained if there were fewer matching declarations, fewer
     1387subexpressions yet to resolve, or possibly fewer possible types the expression
     1388could resolve to. Ordering the expressions in a priority-queue by this metric
     1389would not necessarily produce a top-down or a bottom-up order, but would add
     1390opportunities for pruning based on memoized upper and lower bounds.
     1391
    13841392Both Baker and Cormack explicitly generate all possible interpretations of a
    13851393given expression; thinking of the set of interpretations of an expression as a
Note: See TracChangeset for help on using the changeset viewer.