Jonathan Coates

Yep, sorry - haven't got round to looking at those. Wasn't honestly expecting them to fail.

I've added an integer float function (``5 `mod` 2``). Not sure of a good name for a float-based one though, unless we make it a type class.

Looks like our nightly build is having some issues. I'll have a look and see what I can do. Thanks for mentioning this - I'm not very good at keeping...

So one potentially neat thing that CamlP4 does is using `and` instead of `*` for constructors. So one might have declare lists like so instead: ```ml type list 'a =...

Now that v3.15 of the protocol has been released, it'd be worth adding support for [diagnostic tags][tags]. This is used in VS Code to render unused variables and deprecated variables...

Fixing this would also allow us to remove this disaster: https://github.com/amuletml/amulet/blob/7d2f15a08dee8461bfb044a05caa10f5f30a51de/lib/amulet/category.ml#L50-L51

As a note to myself, see [section 15 of the F# specification](https://fsharp.org/specs/language-spec/4.1/FSharpSpec-4.1-latest.pdf), which is where much of the context system's ideas come from.

Instances should bring their methods into scope within the instance body, but apparently we overlooked that. Sorry! A temporary workaround would be placing `open Exception` somewhere before your definition.

So this is _technically_ working as expected, it's just very bad naming. `range` takes after Haskell's range operators. Where `[1,3..9]` is a shorthand for `[1,3,5,7,9]`. You can see this in...

> Without looking too deeply into this, why cant we just use root project? Instead of having to walk, and then find root? Ahh, sorry! Should have explained this a...