Export typed vars with contracts to untyped namespaces

Description

Problem

While statically typed vars are statically checked, we can just call them from an untyped context and pass any data we please. Gradual typing says this is bad, as errors are delayed and are worse.

Solution

We take a similar approach to Typed Racket. Each typed def will actually define two vars.

The first var is has a munged name, but otherwise represents the original def exactly.

The second var has the original name, but the static type is used as a contract. It also uses the fully expanded AST from the original var.

How to compile typed def's

Here's how we compile a def in typed file.

Take the following typed function my-plus.

Then we emit a def that is the same as the original but with a new name.

Finally we create a new def for my-plus___typed that casts to appropriate

Potholes

  • Recursive functions

    • Which var to rewrite to in the body?

  • Keeping vars up to date

    • What happens on alter-var-root! or def

    • Is it just now part of the semantics? "Deal with it"?

Pull request: 98

Environment

None

Activity

Show:
Ambrose Bonnaire-Sergeant
December 3, 2017, 10:52 PM

Moving away from gradual typing.

Declined

Assignee

Ambrose Bonnaire-Sergeant

Reporter

Ambrose Bonnaire-Sergeant

Labels

Approval

None

Patch

None

Fix versions

Priority

Major