MétaCan
Menu
Back to cohort
Record W2397205586

One Vote for Type Families in Haskell

2008· article· en· W2397205586 on OpenAlexaffabout
Louis-Julien Guillemette, Stefan Monnier

Bibliographic record

VenueTrends in Functional Programming · 2008
Typearticle
Languageen
FieldComputer Science
TopicLogic, programming, and type systems
Canadian institutionsUniversité de Montréal
Fundersnot available
KeywordsHaskellComputer scienceProgramming languageFunctional programmingData typeType (biology)SketchType inferenceType safetyCompilerAbstract data typeData structureContext (archaeology)Theoretical computer scienceClass (philosophy)Modularity (biology)Type theoryArtificial intelligenceAlgorithmInference
DOInot available

Abstract

fetched live from OpenAlex

Generalized Algebraic DataTypes (GADTs) allow programmers to capture important invariants of their data structures through type annotations on data constructors. However when working with GADTs, it is often difficult to concisely and precisely express the way complex data manipulations maintain those invariants. One can approach the problem in a few different ways, given the arsenal of GHC’s current type extensions. One approach is to use type classes with functional dependencies. Another approach is to introduce yet more GADTs to capture the behavior of individual functions. A third alternative is to use type families, a recent introduction of GHC by which functions over types can be defined directly, much like term-level functions, and appear in type signatures. In this paper we illustrate the use of type families in the context of a typepreserving compiler written in Haskell. We compare the results with an ad-hoc, all-GADT solution. We argue that type families promote a more direct programming style that eliminates much code bloat and translates into increased run-time performance. They offer better modularity and require fewer type annotations than type classes, which require that class constraints be propagated between compilation phases. We also describe a use of type families to capture more complex data structure invariants. We mention current limitations that we face with these more advanced uses, in which we need to convince the type checker that the type families we define satisfy certain properties. We sketch a proposal of a language extension to directly support such properties. ?Universite de Montreal, C.P. 6128, succ. Centre-Ville, Montreal, Quebec, Canada. ++1 (514) 343-6111 x3545; {guillelj,monnier}@iro.umontreal.ca

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.918
Threshold uncertainty score0.644

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.107
GPT teacher head0.293
Teacher spread0.186 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designOther design
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations5
Published2008
Admission routes2
Has abstractyes

Explore more

Same venueTrends in Functional ProgrammingSame topicLogic, programming, and type systemsFrench-language works237,207