Haskell 98 language and libraries : the revised report
By P. Jones, L. Simon. 2003
1,461 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/6e80b23963b092a80eeae92ce46648e2ab8b1f54
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Charles E. Leiserson
- Manish Vachharajani
- Jeremy G. Siek
- Yuan Tang
- Rezaul Alam Chowdhury
- Bradley C. Kuszmaul
- Chi-Keung Luk
- Seif Haridi
Citations in the corpus
- Google's MapReduce programming model - Revisited (2007, background): “(We tend to restrict ourselves to Haskell 98 [24], and point out deviations.”
- Gradual typing with unification-based inference (2008, background): “Gradual typing, recently introducedby Siek andTaha [47], enables programmers to mix static and dynamic type checking in a program by providing a convenient way to control which parts of a program are statically checked.”
- Functional Logic Programming: From Theory to Curry (2013, unknown): “The following example shows that Curry is an improvement compared to Haskell which does not have a similar behavior for all inductively sequential operations.”
- A faster algorithm for calculating hypervolume (2006, unknown): “9–12 show the resulting comparisons.”
- Concepts, Techniques, and Models of Computer Programming (2004, background): “We give a brief introduction to Haskell, a popular functional programming language supported by a number of interpreters and compilers [85, 148].”
- The Continuous pi-Calculus: A Process Algebra for Biochemical Modelling (2008, methodology): “The tool is written in Haskell [26,27], and generates ODEs in a format suitable for numerical analysis by Octave [28,29].”
- The pochoir stencil compiler (2011, methodology): “Because our prototype Haskell compiler does not contain a complete C++ front end, however, it sometimes may not understand unusually complex C++ code written by the user, in which case, it employs the -split-macro-shadow optimization, relying on Phase 1 to ensure that the code is Pochoir-compliant.”