Content deleted Content added
m →top: stray comma cleanup + AWB genfixes, replaced: journal = Ecological Informatics, | → journal = Ecological Informatics | |
Citation bot (talk | contribs) m Alter: number. Add: pages, issue, volume, doi. Removed parameters. Formatted dashes. | You can use this bot yourself. Report bugs here. | User-activated. |
||
Line 54:
| year = 2015
| url = http://www.vldb.org/pvldb/vol8/p1892-bux.pdf
| doi = 10.14778/2824032.2824094
}}</ref><ref>
{{Cite journal
Line 90 ⟶ 91:
| title = Lambda calculus as a workflow model
| journal = Concurrency Computat.: Pract. Exper., 21: 1999-2017
| volume = 21
| issue = 16
| pages = 1999–2017
| doi = 10.1002/cpe.1448}}</ref><ref>
{{cite journal
Line 105 ⟶ 109:
| journal = Ecological Informatics
| volume = 5
| number = 1
| pages = 42–50
| year = 2010
| doi = 10.1016/j.ecoinf.2009.08.008 }}
</ref>
In this, Cuneiform is distinct from related workflow languages based on [[dataflow programming]] like [[Swift (parallel scripting language)|Swift]] or Nextflow.<ref>
Line 125 ⟶ 128:
| pages = 316–319
| year = 2017
| doi = 10.1038/nbt.3820 }}
</ref>
Line 155 ⟶ 157:
| volume = 27
| year = 2017
| doi = 10.1017/S0956796817000119 }}
</ref> While Cuneiform provides lists as compound data types it omits traditional list accessors (head and tail) to avoid the possibility of runtime errors which might arise when accessing the empty list. Instead lists are accessed in an all-or-nothing fashion by only mapping or folding over them. Additionally, Cuneiform omits (at the organizational level) arithmetics which excludes the possibility of division by zero. The omission of any partially defined operation allows to guarantee that runtime errors can arise exclusively in foreign code.
| |||