Skip to content

Use an explicit type for type errors #745

@paf31

Description

@paf31

This is a first step toward moving to transformers-0.4.* and ExceptT. We need to:

  • add a type (not String) for errors
  • replace calls to strMsg with the appropriate constructor everywhere.
  • update monad-unify to provide an appropriate error type, and handle that error type in TypeChecker.Monad.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions