This is a prototype implementation of Idris 2.
It is intended to be mostly backwards compatible with Idris 1, with some minor exceptions. The most notable user visible differences, which might cause Idris 1 programs to fail to type check, are:
- Unbound implicit arguments are always erased, so it is a type error to attempt to pattern match on one.
- Simplified resolution of ambiguous names.
- Minor differences in the meaning of export modifiers
public export, which now refer to visibility of names from other namespaces rather than visibility from other files.
- Module names must match the filename in which they are defined (unless the module's name is "Main").
- Anything which uses a
%languagepragma in Idris 1 is likely to be different. Notably, elaborator reflection will exist, but most likely in a slightly different form because the internal details of the elaborator are different.
Preludeis much smaller (and easier to replace with an alternative).
Watch this space for more details and the rationale for the changes, as I get around to writing it...
Summary of new features:
- A core language based on "Quantitative Type Theory" which allows explicit annotation of erased types, and linear types.
letbindings are now more expressive, and can be used to define pattern matching functions locally.
- Names which are in scope in a type are also always in scope in the body of the corresponding definition.
- Better inference. Holes are global to a source file, rather than local to
a definition, meaning that some holes can be left in function types to be
inferred by the type checker. This also gives better inference for the types
caseexpressions, and means fewer annotations are needed in interface declarations.
- Better type checker implementation which minimises the need for compile time evaluation.
- New Chez Scheme based back end which both compiles and runs faster than the default Idris 1 back end. (Also, optionally, Chicken Scheme and Racket can be used as targets).
- Everything works faster :).
A significant change in the implementation is that there is an intermediate
TTImp, which is essentially a desugared Idris, and is cleanly
separated from the high level language which means it is potentially usable
as a core language for other high level syntaxes.
To build and install what exists of it so far:
- Optionally, set the
- This builds the main executable
blodwen, and a minimal dependently typed language with implicit syntax,
ttimp. Most likely you'll only need
ttimpis useful for testing/debugging.
- This builds the main executable
You'll need to set your
You may also want to set
clang, since this seems to build
the generated C significantly faster.
Note: If you edit
blodwen.ipkg to use the
opts with optimisation set
--cg-opt -O2) you'll find it runs about twice as fast, at the cost of
taking a couple of minutes to generate the
I make no promises how well this works yet, but you are welcome to have a play. Good luck :).
(Why "Blodwen"? The answer is here: http://ivortheengine.wikia.com/wiki/Idris)
Things still missing
- Some high level syntax, notably records, 'with', dependent pairs, and numeric ranges
- Cumulativity and totality checking
- Codata (or rather, you can have it, but there's no productivity check...)
- Parts of the ide-mode
- Documentation strings
- The rest of this "Things still missing" list