John Ericson

> Even better would be having e.g. a blog post that puts it all in context, and then somehow linking to that in the messages. Yes a blog post would...

With https://github.com/ghc-proposals/ghc-proposals/pull/448, we could pretty print ``` g @a y = length [x, y] ``` to show the reach. The message could be something like > \ > > With...

Per https://github.com/haskell/error-messages/issues/44 I think we can do this without baking a bunch of logic in GHC, and keeping it in libraries instead. ```haskell instance TypeError (Text "strings are not numbers")...

I wrote in #44 that it's not just a aesthetic distaste for ad-hoc solution that motivates, but also a fear of creeping additional wired in identifier and GHC--library couplings. I...

That sounds good.

Assuming (knock on wood) https://github.com/ghc-proposals/ghc-proposals/pull/448 gets accepted, we have some new stuff to consider here. ```haskell module ErrMsg where f :: forall a. a -> a f x = y...

@cmacrae Wow. Totally coincidentally, I was just today looking into supporting cross compilation to illumos in Nixpkgs, a long-standing personal goal that sat at the back of my mind while...

@cmacrae Heavy guidance is fine. I must admit I have somewhat limited time, but so far it's worked well where I've advised a number of people working on specific cross...

A good first step for you would be trying to add the Illumos linker to nixpkgs (to be built with regular Linux stdenv and packages). Does that sound doable to...

I would be more than happy to make a PR with the changes, but I figured I should open an issue first.