Documentation

Some information about the source code.

Computes a SourceInfo record for the given file.

Is the aim to type-check the top-level module, or only to scope-check it?

Are we loading the interface for the user-loaded file or for an import?

Should state changes inflicted by createInterface be preserved?

Merge an interface into the current proof state.

Scope checks the given module. A proper version of the module name (with correct definition sites) is returned.

If the module has already been visited (without warnings), then its interface is returned directly. Otherwise the computation is used to find the interface and the computed interface is stored for potential later use (unless the MainInterface is MainInterface ScopeCheck).

Type checks the main file of the interaction. This could be the file loaded in the interacting editor (emacs), or the file passed on the command line.

First, the primitive modules are imported. Then, getInterface' is called to do the main work.

If the Mode is ScopeCheck, then type-checking is not performed, only scope-checking. (This may include type-checking of imported modules.) In this case the generated, partial interface is not stored in the state (stDecodedModules). Note, however, that if the file has already been type-checked, then a complete interface is returned.

Tries to return the interface associated to the given (imported) module. The time stamp of the relevant interface file is also returned. Calls itself recursively for the imports of the given module. May type check the module. An error is raised if a warning is encountered.

Do not use this for the main file, use typeCheckMain instead.

See getInterface.

A more precise variant of getInterface. If warnings are encountered then they are returned instead of being turned into errors.

Check if the options used for checking an imported module are compatible with the current options. Raises Non-fatal errors if not.

Check whether interface file exists and is in cache in the correct version (as testified by the interface file hash).

Try to get the interface from interface file or cache.

Run the type checker on a file and create an interface.

Mostly, this function calls createInterface. But if it is not the main module we check, we do it in a fresh state, suitably initialize, in order to forget some state changes after successful type checking.

Formats and outputs the Checking, Finished and "Loading " messages.

Print the highlighting information contained in the given interface.

Read interface file corresponding to a module.

Writes the given interface to the given file.

The written interface is decoded and returned.

Tries to type check a module and write out its interface. The function only writes out an interface file if it does not encounter any warnings.

If appropriate this function writes out syntax highlighting information.

Collect all warnings that have accumulated in the state.

Expert version of getAllWarnings; if isMain is a MainInterface, the warnings definitely include also unsolved warnings.

Reconstruct the iScope (not serialized) from the iInsideScope (serialized).

Builds an interface for the current module, which should already have been successfully type checked.

Returns (iSourceHash, iFullHash) We do not need to check that the file exist because we only accept InterfaceFile as an input and not arbitrary AbsolutePath!

True if the first file is newer than the second file. If a file doesn't exist it is considered to be infinitely old.