engineering peer review

[KiaraGrouwstra]

I feel like on the engineering side I've picked some libraries where nicer options might be available, notably using a combination of haskell-src-exts and hint for respectively constructing and evaluating ASTs as opposed to using ghc-lib / ghc-lib-parser to stick with native functionality.

things I'm using the interpreter for:

• indirectly, instantiateTypes / zonking
• matchesConstraints / type matching
• fnIoPairs / evaluating functions on their sample inputs to get outputs (for dataset generation seemingly my main performance culprit, see run-time performance #5)
• exprType: get the type of an expression
• genInputs: generate examples -- this part only works on concrete (instantiated) types not containing functions 😐, but that's on QuickCheck that I'm using for this (if thru the interpreter).
• fitExpr: check if a candidate fits into a hole by just type-checking the result through the interpreter (then checking if the expression type is still a function if using currying over lambdas).

some places I may wanna check for inspiration:

• djinn / djinn-ghc:
  • no haskell-src-exts but uses its own AST thing
  • according to Help Djinn does *not* instantiate polymorphic functions, which sounds... worse than my thing? tho for generation mine is still undirected brute-force...
  • seems interactive like holes in Idris
  • uses a theorem prover and propositional logic
  • does fun stuff like etaReduce (which I wanna delegate to hlint (synthesize legible programs #22) and equivalence/matching logic which may be of interest to me for deduping types/expressions...
• hoogle: also uses haskell-src-exts tho no hint. question: can I learn from their type matching to get rid of some interpreter calls?
• the awesome Tweag I/O's ormolu, which using reverse dependency search I found uses ghc-lib-parser. this handles parsing and printing.
• /r/haskell to get my engineering decisions on this peer-reviewed: posted here.