Louis Pilfold

I should join the mailing list :)

Ah, I may have to reinstall the irc client. With Elixir, Erlang, Elm and the companies I've worked for all being on slack I've not used it in some time.

Only top level expressions have exhaustiveness checking at present -> https://github.com/alpaca-lang/alpaca#using-it

Would any overhead would be introduced by wrapping functions like that?

What's the rationale for this? :)

Sounds sensible to me, though I could see some unions needing qualification and some not being confusing.

```elm opaque type set 'a type t = Int int | Set set 'a let foo x = match x with | Int i -> "got an integer" | Set...

Another alternative could be a system like Purescripts `Foreign` and Elm's `Json`, where from FFI we get an opaque foreign value that we have to explicitly attempt to decode with...

I see the docs prefer snake_case too. I could update these? :)

As a data point Purescript is in the process of switching from Eff to the simpler IO. I think the general opinion is that it added a lot of complexity...