Ultimately, if reading error messages did require linking with GHC, it
wouldn't be the end of the world. I would just write my own
translation layer to JSON. So consider this a weak preference.
I think this is the key. Ultimately, all other uses can be done on top
of just linking GHC the l
> On May 3, 2021, at 3:11 PM, Chris Smith wrote:
>
> Thanks, Richard. This is awesome!
Glad you're excited. I am, too!
>
> For my use case, the more exciting possibility would be to interact with
> error messages from JavaScript. For this reason, I'd definitely love to see
> a well-known
Thanks, Richard. This is awesome!
For my use case, the more exciting possibility would be to interact with
error messages from JavaScript. For this reason, I'd definitely love to
see a well-known structured file format (JSON, YAML, XML, or whatever) that
can be read without linking against GHC.
Hi all,
Alfredo and I are hard at work redesigning GHC's error-message system. It is
time for more input, though, from clients of the system -- those writing IDEs
and other tooling on top of GHC.
The key question: How would you like your errors served?
Right now, errors are served well-done: f
