About: Total functional programming     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : yago:WikicatProofAssistants, within Data Space : dbpedia.org associated with source document(s)

Total functional programming (also known as strong functional programming, to be contrasted with ordinary, or weak functional programming) is a programming paradigm that restricts the range of programs to those that are provably terminating. Termination is guaranteed by the following restrictions: for division); adding another argument to specify the result for those inputs; or excluding them by use of type system features such as refinement types. To make it substructural recursive using the length of the vector as a limit, we could do:

AttributesValues
rdf:type
rdfs:label
  • Total functional programming
rdfs:comment
  • Total functional programming (also known as strong functional programming, to be contrasted with ordinary, or weak functional programming) is a programming paradigm that restricts the range of programs to those that are provably terminating. Termination is guaranteed by the following restrictions: for division); adding another argument to specify the result for those inputs; or excluding them by use of type system features such as refinement types. To make it substructural recursive using the length of the vector as a limit, we could do:
sameAs
dct:subject
Wikipage page ID
Wikipage revision ID
Link from a Wikipage to another Wikipage
foaf:isPrimaryTopicOf
prov:wasDerivedFrom
has abstract
  • Total functional programming (also known as strong functional programming, to be contrasted with ordinary, or weak functional programming) is a programming paradigm that restricts the range of programs to those that are provably terminating. Termination is guaranteed by the following restrictions: 1. * A restricted form of recursion, which operates only upon ‘reduced’ forms of its arguments, such as Walther recursion, substructural recursion, or "strongly normalizing" as proven by abstract interpretation of code. 2. * Every function must be a total (as opposed to partial) function. That is, it must have a definition for everything inside its domain. 3. * There are several possible ways to extend commonly used partial functions such as division to be total: choosing an arbitrary result for inputs on which the function is normally undefined (such as for division); adding another argument to specify the result for those inputs; or excluding them by use of type system features such as refinement types. These restrictions mean that total functional programming is not Turing-complete. However, the set of algorithms that can be used is still huge. For example, any algorithm for which an asymptotic upper bound can be calculated (by a program that itself only uses Walther recursion) can be trivially transformed into a provably-terminating function by using the upper bound as an extra argument decremented on each iteration or recursion. For example, quicksort is not trivially shown to be substructural recursive, but it only recurs to a maximum depth of the length of the vector (worst-case time complexity O(n2)). A quicksort implementation on lists (which would be rejected by a substructural recursive checker) is, using Haskell: qsort [] = []qsort [a] = [a]qsort (a:as) = let (lesser, greater) = partition a as in qsort lesser ++ [a] ++ qsort greater To make it substructural recursive using the length of the vector as a limit, we could do: qsort x = qsortSub x x-- minimum caseqsortSub [] as = as -- shows termination-- standard qsort casesqsortSub (l:ls) [] = [] -- nonrecursive, so acceptedqsortSub (l:ls) [a] = [a] -- nonrecursive, so acceptedqsortSub (l:ls) (a:as) = let (lesser, greater) = partition a as -- recursive, but recurs on ls, which is a substructure of -- its first input. in qsortSub ls lesser ++ [a] ++ qsortSub ls greater Some classes of algorithms that have no theoretical upper bound but have a practical upper bound (for example, some heuristic-based algorithms) can be programmed to "give up" after so many recursions, also ensuring termination. Another outcome of total functional programming is that both strict evaluation and lazy evaluation result in the same behaviour, in principle; however, one or the other may still be preferable (or even required) for performance reasons. In total functional programming, a distinction is made between data and codata—the former is finitary, while the latter is potentially infinite. Such potentially infinite data structures are used for applications such as I/O. Using codata entails the usage of such operations as corecursion. However, it is possible to do I/O in a total functional programming language (with dependent types) also without codata. Both Epigram and Charity could be considered total functional programming languages, even though they don't work in the way Turner specifies in his paper. So could programming directly in plain System F, in Martin-Löf type theory or the Calculus of Constructions.
http://purl.org/voc/vrank#hasRank
is Link from a Wikipage to another Wikipage of
is Wikipage redirect of
is Wikipage disambiguates of
is foaf:primaryTopic of
Faceted Search & Find service v1.17_git39 as of Aug 09 2019


Alternative Linked Data Documents: PivotViewer | iSPARQL | ODE     Content Formats:       RDF       ODATA       Microdata      About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3235 as of Sep 1 2020, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (61 GB total memory)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2020 OpenLink Software