6This section provides highlights of the Idris compilation process, and
7provides details over how you can follow the process through logging.
12Idris follows the following compilation process:
25 #. Defunctionalisation
27 #. Resolving variables
34With Idris you can ask it to terminate the compilation process after type checking has completed. This is achieved through use of either:
36+ The command line options
38 + ``--check`` for files
39 + ``--checkpkg`` for packages
41+ The REPL command: ``:check``
43Use of this option will still result in the generation of the Idris binary ``.ibc`` files, and is suitable if you do not wish to generate code from one of the supported backends.
48Logging of the Idris output can be used to diagnose problems with the compilation of your program.
49Idris supports the logging at various different levels of verbosity: 1 to 10.
51+ Level 0: Show no logging output. Default level
52+ Level 1: High level details of the compilation process.
53+ Level 2: Provides details of the coverage checking, and further details the elaboration process specifically: Class, Clauses, Data, Term, and Types,
54+ Level 3: Provides details of compilation of the IRTS, erasure, parsing, case splitting, and further details elaboration of: Instances, Providers, and Values.
55+ Level 4: Provides further details on: Erasure, Coverage Checking, Case splitting, and elaboration of clauses.
56+ Level 5: Provides details on the prover, and further details elaboration (adding declarations) and compilation of the IRTS.
57+ Level 6: Further details elaboration and coverage checking.
61+ Level 10: Further details elaboration.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list