Alistair

Hey 👋 Following up to see if there's anything I need to do on my side. If not, what are the next steps to move this RFC forward?

Thanks for the update! 🙏 A few thoughts from my side: - I'm still not convinced by the 'tuple polymorphism' direction. It's a large change to the typer, and it...

> My understanding of the majority opinion that (numeric) tuple projections should not require type information is as follows: in everyone's mental model of OCaml untyped semantics, tuple access `x.2`...

We could introduce some row-like syntax for the head of the tuple e.g. infer `(.. * 1:'a * ..) -> 'a` for `.1` You could infer something similar for labelled...

> Note that I have tested some quick prototypes for deserializers and a bridge between the proposed compiler diagnostic and the grace library at https://github.com/Octachron/sdiag-prototypes . Its lovely to see...

This shouldn't be too difficult, the addition of 'contextual lines' is handled here: https://github.com/johnyob/grace/blob/c8aa9abfd69250b5610f8d7d1e1e914f1d748b9d/lib/ansi_renderer/snippet.ml#L339 By default we add +- 1 lines for contextual lines around multi-line labels. We can easily...

Hey 👋 Perhaps we should attach a location with the main message that we write for a diagnostic: ```ocaml type 'code t = { severity : Severity.t ; message :...

As for more ambitious plans for LSP integration, the first step I had in mind was a `Grace_lsp` library, which just adds support for converting between Grace's types and LSP...

Hey 👋 > Unless I cannot find the correct API, it looks like it is only possible to create diagnostics using byte indexes within the source. Yes, only byte-oriented positions...

> What parsing library are you using? Both Menhir and Sedlex will be able to give you byte-oriented positions I did some digging -- I assume this issue is related...