Design and implement a decent type checking algorithm #16
Labels
No labels
blocked
blocker
bug
c
codegen
dependencies
discussion
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
javascript
lexer/parser
llvm
macroexpander
performance
priority:high
priority:low
priority:normal
question
triage
typechecker
webassembly
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: samvv/bolt#16
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ideally, we'd like to implement a type system that from the very start can easily be extended with custom rules. For this, we will probably need a specialized tool that can evaluate typing rules at compile-time. One such (experimental) tool is currently in the making by @samvv and hopefully will be integrated in time for the second milestone.
After doing some research, we're going a different route. The type system will be roughly based on the well-known Hindley-Milner type system, which enables us to implement typeclasses quite naturally.
Already fixed in another repository.