A type-checker for the λΠ-modulo calculus.
Define a parser. Play it in reverse to get a pretty printer.
A solution to boolean blindness.
A pure Haskell implementation of the 9p protocol, server and client.
An encoding of the Calculus of Inductive Constructions (as implemented in Coq) in Dedukti.
Incremental serialization and deserialization of Haskell values.
An efficient, embeddable DPLL SAT solver in Haskell
Command-line access to xe.com
Burndown charts for Asana.
I don't think clashing file extensions are a problem per say. Case in point: there are currently four separate entries registered in Linguist's
language.yaml for the
.ncl extension. Nickel would just add a fifth. Another example would be both Perl and Prolog using the
.pl extension. Arguably, the intersection of NACL users and Nickel users is even smaller than the intersection of Perl and Prolog users. GitHub does not use file extensions exclusively as the way to determine which language appears in a given file. In fact it's not even the first strategy. See here. However, if we do stick to
.ncl then we indeed should make a PR against github/linguist to make detection of Nickel more accurate.
.ncl can stand for Nickel as well as for Nickel Configuration Language or Nix Configuration Language. The "cl" part is quite nice to have in the name.
comment created time in 3 months