So the Name.Tracker type only needs to track one set, rather than two
for each sort of dependency.

It now lives in the object graph nodes, so it makes sense to have all
the details in one place.

It is used in a decent number of places in code gen

When we have type information, it’ll be possible to do this more often.
Nonetheless, this should...

The code gets a decent bit simpler thanks to the improvements in
earlier phases:

- There is no ...

For example, each case expression saves a temporary variable just in
case. That means we do all ...

This makes it easier to delay decisions about how code should be
generated.

This will make it easier to generate integer identifiers when
generating production code (but st...

Fix a typo

The graph nodes are set up for cyclic values, tail calls, and effect
managers. This also tracks ...

If we know the frequency of each field, we can assign them short/unique
names. So the 53 most us...

So far it converts everything except for case expressions. Need to make
some choices about how c...

The plan is to rely on JS minifiers for inlining of single-use
variables.

Longer-term, we would...

The main goals here are:

1. Gather usage counts for each argument. This will make it easier to
...

string-based-check: Single file per message
Drop filename from messages
Fix JS bindings
Clenaup
B...

This organizes all the constraints from the value declarations and the
ports/effects in the modu...

Instead of a custom Solver monad, the new Type.Solve code uses plain IO
and threads some state a...

string-based-check: some cleanup

They will always be prefixed, so it is silly to follow that Haskell
convention of repeating the ...

Rather than using a ErrorT/StateT/IO monad stack, the new code uses a
CPS’d version that only tr...

I noticed that every use of CLet had a list like [Scheme] where there
was only one scheme. So ra...

The old version builds Bags as you go, turning it into dictionary at
the end. That means adding ...

Create new “Expectation” type that holds context information about why
certain things should be ...

Docs: Fix typo, split installation commands

Use a new format for error reporting. It provides both the Context of
the constraint and the Cat...

This introduces the AST.Canonical.Annotation type that holds on to all
the free type variables i...

The code seems to be better if it is more explicit on these points.

Remove the AST.Type module and distribute it between AST.Source,
AST.Canonical, and AST.Utils.Type

All this logic moves to constraining expressions and patterns
specifically. This makes it easier...

Rather than having all the logic that uses the core code in these
modules, the special uses are ...

This change started because I could not remember if an Int was
zero-indexed or one-indexed. Now ...