A dependently typed programming language, a successor to Idris
Go to file
Edwin Brady 4ccddbac4a Don't generalise to RigW on let types
This is just as ugly as the similar hack for lambdas in 413d09da, but
necessary to allow let binding of linear functions.
2020-02-11 17:54:11 +00:00
.ci-dockerfiles Add Travis CI config 2019-07-23 21:49:24 +02:00
.github/ISSUE_TEMPLATE Update issue templates 2019-07-23 09:43:18 +01:00
docs Use HTTPS instead of HTTP 2019-12-18 21:37:50 +01:00
icons Add icons/logos 2019-07-21 14:47:11 +01:00
libs Add nub to Data.List 2020-02-09 21:45:36 +00:00
Notes Use HTTPS instead of HTTP 2019-12-18 21:37:50 +01:00
src Don't generalise to RigW on let types 2020-02-11 17:54:11 +00:00
support Add System.Directory 2020-02-01 18:43:28 +00:00
tests Implement 'using' notation 2020-02-11 17:27:04 +00:00
.gitignore Improve RTD config. 2019-07-31 14:07:16 +01:00
.travis.yml Add Travis CI config 2019-07-23 21:49:24 +02:00
CONTRIBUTING.md Delay should always delay, not just under Inf 2019-08-06 14:54:27 +01:00
idris2.ipkg Begin elaboration of quoting terms 2019-11-30 15:26:17 +00:00
INSTALL.md Use HTTPS instead of HTTP 2019-12-18 21:37:50 +01:00
LICENSE Remember to add the LICENSE 2019-07-09 00:00:25 +02:00
Makefile Only use version tag in display 2020-01-30 18:25:18 +00:00
README.md Don't generalise to RigW on let types 2020-02-11 17:54:11 +00:00
tests.ipkg Added test framework (copied from Blodwen) 2019-05-07 10:43:02 +01:00
TypeDD.md Better approach to erasure in pattern matching 2020-01-21 18:47:43 +00:00

Idris 2

This is a pre-alpha implementation of Idris 2, the successor to Idris.

*** Please note: To build, these requires Idris version 1.3.2 ***

Idris 2 is 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, which might mean you need to explicitly disambiguate more often. As a general rule, Idris 2 will be able to disambiguate between names which have different concrete return types (such as data constructors), or which have different concrete argument types (such as record projections). It may struggle to resolve ambiguities if one name requires an interface to be resolved.
  • Minor differences in the meaning of export modifiers private, export, and 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 %language pragma 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.
  • The Prelude is 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.
  • let bindings 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 of case expressions, 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 language 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.

Installation

To build and install what exists of it so far:

  • Optionally, set the PREFIX in Makefile
  • make idris2
  • make install

You'll need to set your PATH to $PREFIX/bin You may also want to set IDRIS_CC to clang, since this seems to build the generated C significantly faster.

Note: If you edit idris2.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 idris2 executable.

You can check that building succeeded by running

  • make test

I make no promises how well this works yet, but you are welcome to have a play. Good luck :).

Information about external dependencies are presented in INSTALL.md.

Things still missing

  • Disambiguation via 'with'
  • Cumulativity (so we currently have Type : Type! Bear that in mind when you think you've proved something :))
  • 'rewrite' doesn't yet work on dependent types
  • Parts of the ide-mode, particularly syntax highlighting
  • Documentation strings and HTML documentation generation
  • ':search' and ':apropos' at the REPL
  • The rest of this "Things still missing" list

Talks

Idris 2 - Type-driven Development of Idris (Curry On - London 2019)